← ClaudeAtlas

add-commandlisted

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
rajdeepratan/SlashForge · ★ 5 · AI & Automation · score 73
Install: claude install-skill rajdeepratan/SlashForge
# 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 hand