new-command
Skill4 starsChanged 20 days agoMITView on GitHub
Read when adding or changing a scip-cli CLI subcommand.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- brycewc/domo-scriptstheir own version, first seen Nov 8, 2026
- pnp/cli-microsoft365their own version, first seen Oct 8, 2026
- ivuorinen/skillstheir own version, first seen Sep 24, 2026
- santree-ai/santreetheir own version, first seen Jul 31, 2026
- cortex-tms/cortex-tmstheir own version, first seen Feb 23, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- pnp/cli-microsoft365★ 1.5ksame name
- cortex-tms/cortex-tms★ 180same name
- santree-ai/santree★ 14same name
- ivuorinen/skills★ 4same name
- brycewc/domo-scripts★ 1same 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 repository4 other files it gives its agents.
- .cursor/rules/agent.mdcCursor rule
- sql-benchSkill
- testSkill
- scip-cliSkill
The file
Files
New or changed CLI command
User-facing reference lives in scip_cli/SKILL.md + README.md (must match scip_cli/__main__.py flags). Run scip-cli skill to verify dump.
Checklist
scip_cli/commands/<name>.py—main(args); thin handler. Usesession.setup()for index DB unless the command isreindex/skill.scip_cli/__main__.py— import;add_parser; wiredispatch["<name>"] = <module>.main.- Shared flags — reuse
scip_cli/cli_args.py(add_path_argument,add_limit_argument, …) when siblings use them. - SQL — keep queries in
scip_cli/queries.pyorscip_cli/analyze/, not fat command modules. - Docs — quick-guide row +
### <name>section inscip_cli/SKILL.md; bullet in README § Commands. - Tests —
tests/test_e2e.py(ortest_e2e_analyze_patterns.pyfor analyze-only); addscip_cli.commands.<name>.setuptotests/e2e_harness.pyCOMMAND_SETUP_PATHS. - Verify — follow skill
test; run narrowed pytest then e2e loop.
Patterns
- Read-only DB:
db, project_root = setup()intry/finally: db.close(). Connection already hasconfigure_read_connectionviaget_db. - Errors: raise
RuntimeErroror letsqlite3.Errorbubble —__main__.mainmaps them to stderr + exit code. - Output: stdout = records; stderr = warnings (match existing commands).
Map
| Concern | Path |
| Entry / argparse | scip_cli/__main__.py |
| Handlers | scip_cli/commands/ |
| Index open | scip_cli/session.py, scip_cli/indexing/core.py |
| User skill install | scip-cli skill <path> copies scip_cli/SKILL.md |
Cursor repo conventions
- Skills (
.cursor/skills/<name>/, frontmattername:= folder name): agent reads when the task matches — e.g.test,sql-bench,new-command. - Commands (
.cursor/commands/): only workflows you invoke with slash — e.g.dogfood,migration-problems. Never duplicate the same workflow as a skill and a command.
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.

