slashforge

The source repo for SlashForge — a zero-dependency Node CLI that installs spec-driven workflow slash commands (setup, code, investigate, fix, resume, review-pr, test, refactor) into Claude Code, Cursor, and Codex. The product is the templates/ it ships; bin/install.js renders and installs them per host.

Agent orchestration

Project References

The docs/ Astro site is a separate workspace with its own docs/CLAUDE.md, rule, and agent.

Project overview

SlashForge is distributed on npm as slashforge. A user runs the installer, which copies and renders the templates/ into their agent host's config directory. The guides (templates/slashforge-*.md) are read by agents at runtime; the commands and discipline skills (templates/slashforge/*.md) are the invocable entry points.

Tech stack

Commands

npm test                               # run the full node:test suite
node --test test/install.test.js       # run one test file
node bin/install.js --dry-run          # preview an install without writing
node bin/install.js --help             # CLI usage
node scripts/snapshot-claude-render.js # regenerate the pinned Claude render fixture

Docs commands run from docs/ — see docs/CLAUDE.md.

Project structure

bin/install.js            # the installer CLI (renders + installs templates)
templates/
├─ slashforge-*.md        # guide/reference files read by agents at runtime
├─ slashforge/*.md        # commands (setup, code, …) + discipline skills (plan, tdd, …)
├─ agents/                # agent dispatch templates
└─ slashforge-*.{html,sh,js}  # asset files, copied verbatim (no frontmatter)
test/                     # node:test suite + fixtures/ (incl. pinned claude-render)
scripts/snapshot-claude-render.js   # regenerates the pinned fixture
docs/                     # Astro docs site (separate workspace)
docs/slashforge/          # the spec home — constitution, architecture, status, archive
.github/workflows/        # ci.yml, auto-release.yml, publish.yml
.github/scripts/          # check-docs-*.mjs (run against the built docs site)

Architecture overview

• bin/install.js resolves a target (claude / cursor / codex / skills), each with its own render profile — which per-host target blocks to keep and which guides to omit.
• Target blocks (<!--target:x-->…<!--/target-->) fence host-specific wording inside one template. Balance and valid names are enforced by tests.
• The Claude render is pinned byte-for-byte in test/fixtures/claude-render. Any change to Claude output must be reflected by regenerating that fixture.
• Installs are atomic — validation happens before any directory is written.
• See docs/slashforge/architecture.md for the full picture.

Non-negotiable rules (see docs/slashforge/constitution.md)

• Zero runtime dependencies — the installer uses only Node built-ins; never add a dependencies entry.
• Line limits — every guide/command .md ≤ 200 lines (≤ 500 for a SKILL.md); split, never truncate. See .claude/rules/templates.md.
• main is the release trigger — a package.json version bump merged to main publishes to npm. main must always be green and releasable. See .claude/rules/git.md.
• Pinned Claude render — regenerate test/fixtures/claude-render (never hand-edit) when template output changes. See .claude/rules/testing.md.
• Balanced target blocks — every <!--target:x--> has a matching <!--/target-->; only valid target names.
• No secrets committed — publish tokens/2FA live outside the repo; publish uses OIDC with no token.
• Branch as type/short-desc; confirm the base branch before branching.