agentleFS
fleslerflesler/scip-cli/.cursor/skills/new-command/SKILL.md

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

  • Other versions5 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 5

    1. pnp/cli-microsoft365★ 1.5ksame name
    2. cortex-tms/cortex-tms★ 180same name
    3. santree-ai/santree★ 14same name
    4. ivuorinen/skills★ 4same name
    5. 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.

The file

Files
SKILL.md

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

  1. scip_cli/commands/<name>.py — main(args); thin handler. Use session.setup() for index DB unless the command is reindex / skill.
  2. scip_cli/__main__.py — import; add_parser; wire dispatch["<name>"] = <module>.main.
  3. Shared flags — reuse scip_cli/cli_args.py (add_path_argument, add_limit_argument, …) when siblings use them.
  4. SQL — keep queries in scip_cli/queries.py or scip_cli/analyze/, not fat command modules.
  5. Docs — quick-guide row + ### <name> section in scip_cli/SKILL.md; bullet in README § Commands.
  6. Tests — tests/test_e2e.py (or test_e2e_analyze_patterns.py for analyze-only); add scip_cli.commands.<name>.setup to tests/e2e_harness.py COMMAND_SETUP_PATHS.
  7. Verify — follow skill test; run narrowed pytest then e2e loop.

Patterns

  • Read-only DB: db, project_root = setup() in try / finally: db.close(). Connection already has configure_read_connection via get_db.
  • Errors: raise RuntimeError or let sqlite3.Error bubble — __main__.main maps them to stderr + exit code.
  • Output: stdout = records; stderr = warnings (match existing commands).

Map

ConcernPath
Entry / argparsescip_cli/__main__.py
Handlersscip_cli/commands/
Index openscip_cli/session.py, scip_cli/indexing/core.py
User skill installscip-cli skill <path> copies scip_cli/SKILL.md

Cursor repo conventions

  • Skills (.cursor/skills/<name>/, frontmatter name: = 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.