agentleFS
Sign inStart free
rajdeepratanrajdeepratan/SlashForge/.claude/skills/add-command/SKILL.md

add-command

Skill5 starsChanged 35 days agoMITView on GitHub

Add a new user-facing slash command or discipline skill to the kit — use when creating a new /slashforge-* entry point or workflow discipline, wiring it into the installer and snapshot

7 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions7 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 7

    1. redis/go-redis★ 22ksame name
    2. gitkraken/vscode-gitlens★ 10ksame name
    3. microsoft/vscode-cmake-tools★ 1.7ksame name
    4. Doist/todoist-cli★ 331same name
    5. ldayton/Dippy★ 243same name
    6. coralogix/cx-cli★ 241same name
    7. 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/rules/templates.md and .claude/rules/cli.md.

    line 19

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Add a command or discipline skill

The kit ships two kinds of invocable template, both living in templates/slashforge/<name>.md and both installed as slashforge-<name> on every host:

  • Commands (COMMAND_FILES) — the entry points a user types: setup, code, investigate, fix, resume, review-pr, test, refactor. These drive meta.json's commands list and the status output.
  • Discipline skills (SKILL_FILES) — disciplines the workflow invokes on the user's behalf: brainstorm, plan, debug, tdd, verify, request-review, review-feedback, worktree, parallel. Kept out of COMMAND_FILES on purpose so status reports only what users actually type.

Before starting

Read .claude/rules/templates.md and .claude/rules/cli.md. Decide first: is this a user entry point (command) or an internal discipline (skill)? That decides which array it goes in.

Steps

  1. Create templates/slashforge/<name>.md with frontmatter (name, description) and body ≤ 200 lines (≤ 500 if authored as a skill). Use target blocks for host-specific wording — a command often needs a claude vs agents split for how it dispatches reviewers/PRs.
  2. Register it in bin/install.js: add path.join('slashforge', '<name>.md') to COMMAND_FILES (user command) or SKILL_FILES (discipline). Do not put it in both.
  3. Wire references — if it's a command, reference it from CLAUDE.md's orchestration table and any workflow guide that hands off to it. If it's a discipline, make sure the phase that invokes it names it.
  4. Run tests — npm test (spec-features.test.js asserts that shipped commands install correctly).
  5. Regenerate the snapshot and review:
    node scripts/snapshot-claude-render.js
git diff test/fixtures/claude-render
  6. Update CHANGELOG.md under ## [Unreleased]. If it's a new user command, it will also surface in meta.json's commands — mention it in the docs site.

Verify

  • File is within its line limit with valid frontmatter
  • Target blocks balanced; target names valid
  • Added to exactly one of COMMAND_FILES / SKILL_FILES
  • Referenced from CLAUDE.md (commands) or the invoking phase (disciplines)
  • npm test passes
  • Snapshot regenerated and diff reviewed
  • CHANGELOG.md updated

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.

Check your setup, free