What happens if ARGUMENTS is empty?

The CLI defaults to status and runs node bin/cli.js status.

Where is the CLI executed from?

From the project root, using node bin/cli.js with the provided ARGUMENTS.

How do I verify install/uninstall results?

After install, check ~/.claude/statusline.sh exists and ~/.claude/settings.json has the statusLine key. After uninstall, ensure statusline.sh is removed and the statusLine key is removed.

dev-install

npx machina-cli add skill yusufalikync/ccs/dev-install --openclaw

Files (1)

SKILL.md

1.0 KB

Dev Install

Quick shortcut to run the CLI during local development.

Instructions

Run the CLI command based on $ARGUMENTS:

node bin/cli.js $ARGUMENTS

If $ARGUMENTS is empty, default to status.

Post-run Verification

After the command completes, verify the result:

After `install`

Check ~/.claude/statusline.sh exists: ls -la ~/.claude/statusline.sh
Check ~/.claude/settings.json contains statusLine key: read the file and confirm the statusLine configuration is present

After `uninstall`

Confirm ~/.claude/statusline.sh is gone: ls ~/.claude/statusline.sh 2>&1
Confirm statusLine key removed from ~/.claude/settings.json: read the file and check

After `status`

Just display the output — no additional checks needed.

Report what happened and whether verification passed.

Source

git clone https://github.com/yusufalikync/ccs/blob/main/.claude/skills/dev-install/SKILL.mdView on GitHub

Overview

Dev Install provides a quick shortcut to run the project's CLI during local development. It accepts install, uninstall, or status as arguments and executes node bin/cli.js with those arguments. If no argument is supplied, it defaults to status, and post-run checks help validate the outcome.

How This Skill Works

It shells out to node bin/cli.js with the provided ARGUMENTS. If ARGUMENTS is empty, it defaults to status, ensuring a safe default. After execution, follow the post-run verification steps to confirm the outcome.

When to Use It

During local development, install dependencies or set up the local environment with install.
Clean up the local setup by running uninstall.
Check the current CLI state with status to see what is active.
Debug the CLI flow by running with explicit arguments and observing results.
Perform the prescribed post-run verification after install or uninstall to confirm files exist or are removed.

Quick Start

Step 1: Run the CLI with your desired ARGUMENTS, e.g., node bin/cli.js install
Step 2: If ARGUMENTS is empty, the CLI defaults to status
Step 3: Perform the post-run verification steps described for the command you ran

Best Practices

Pass explicit arguments (install, uninstall, or status) to node bin/cli.js instead of relying on defaults.
When you run install, verify ~/.claude/statusline.sh exists and that ~/.claude/settings.json contains a statusLine key.
When you run uninstall, verify that statusline.sh is removed and the statusLine key is removed from settings.json.
If you only need a quick check, use status and avoid extra verification steps.
Run the command from the project root so node bin/cli.js resolves the correct path.

Example Use Cases

node bin/cli.js install
node bin/cli.js uninstall
node bin/cli.js status
node bin/cli.js
Install then verify: ls -la ~/.claude/statusline.sh && cat ~/.claude/settings.json | grep statusLine

Frequently Asked Questions

Add this skill to your agents