add-command
Skill243 starsChanged 8 months agoMITView on GitHub
Add support for a new CLI command. Use when implementing a handler or adding to SIMPLE_SAFE.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- coralogix/cx-clitheir own version, first seen Nov 8, 2026
- Doist/todoist-clitheir own version, first seen Nov 5, 2026
- rajdeepratan/SlashForgetheir own version, first seen Oct 9, 2026
- redis/go-redistheir own version, first seen Oct 8, 2026
- gitkraken/vscode-gitlenstheir own version, first seen Oct 8, 2026
- microsoft/vscode-cmake-toolstheir own version, first seen Apr 20, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- redis/go-redis★ 22ksame name
- gitkraken/vscode-gitlens★ 10ksame name
- microsoft/vscode-cmake-tools★ 1.7ksame name
- Doist/todoist-cli★ 331same name
- coralogix/cx-cli★ 241same name
- rajdeepratan/SlashForge★ 5same name
- Doist/twist-cli★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- check-coverageSkill
- debugSkill
- releaseSkill
- verify-countsSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Add support for $ARGUMENTS in Dippy.
- Very specific: line 28
SIMPLE_SAFE: Always safe regardless of arguments (read-only, no destructive flags).
- Very specific: line 33
Add to SIMPLE_SAFE in src/dippy/core/allowlists.py and add tests to tests/test_simple.py in the appropriate category.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Add support for $ARGUMENTS in Dippy.
1. Research
tldr pages:
ls ~/source/tldr/pages/*/$ARGUMENTS*.md
cat ~/source/tldr/pages/*/$ARGUMENTS.mdCLI docs:
$ARGUMENTS --help
man $ARGUMENTSNote which operations are read-only vs mutations.
2. Decide: Handler or SIMPLE_SAFE?
- SIMPLE_SAFE: Always safe regardless of arguments (read-only, no destructive flags). Go to step 3A.
- Handler: Needs subcommand/flag analysis. Go to step 3B.
3A. SIMPLE_SAFE Path
Add to SIMPLE_SAFE in src/dippy/core/allowlists.py and add tests to tests/test_simple.py in the appropriate category. Skip to step 5.
3B. Handler Path
Create tests/cli/test_$ARGUMENTS.py:
"""Test cases for $ARGUMENTS."""
import pytest
from conftest import is_approved, needs_confirmation
TESTS = [
# Safe operations
("$ARGUMENTS <safe-subcommand>", True),
("$ARGUMENTS --help", True),
# Unsafe operations
("$ARGUMENTS <unsafe-subcommand>", False),
]
@pytest.mark.parametrize("command,expected", TESTS)
def test_command(check, command: str, expected: bool):
result = check(command)
if expected:
assert is_approved(result), f"Expected approve: {command}"
else:
assert needs_confirmation(result), f"Expected confirm: {command}"4. Implement Handler
Create src/dippy/cli/$ARGUMENTS.py:
"""$ARGUMENTS handler for Dippy."""
from dippy.cli import Classification, HandlerContext
COMMANDS = ["$ARGUMENTS"]
SAFE_ACTIONS = frozenset({"list", "show", "status"})
def classify(ctx: HandlerContext) -> Classification:
tokens = ctx.tokens
action = tokens[1] if len(tokens) > 1 else None
if action in SAFE_ACTIONS:
return Classification("allow", description=f"$ARGUMENTS {action}")
return Classification("ask", description="$ARGUMENTS")For handler patterns (nested subcommands, flag-checking, delegation), see patterns.md.
5. Iterate
just testFix failures until tests pass.
6. Verify
just check MUST pass before you're done.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

