Once per repo, before anything else. The largest fixed load of any command, then it writes your agent’s setup.
Workflow slash commands for AI coding agents.
Plan. Gate. Verify. Ship.
One install for Claude Code, Cursor and Codex.
Two runs, start to finish
Shipping a feature
Reviewing someone else's
Eight commands
Each command triggers one distinct workflow/slashforge-setupOne-time repo setup. Explores the codebase, asks clarifying questions, then generates an entry file plus rules, skills, subagents, commands, and hooks tailored to it. Runs on every agent and writes each one’s own layout.
/slashforge-codeEnd-to-end development. Ten phases from plan to merged PR, with mandatory stop-and-confirm gates. Add -quick for lean mode on small changes.
/slashforge-investigateRead-only research. Reproduces and root-causes a bug, then writes a findings report. Never touches your code.
/slashforge-fixPatches a bug straight from an investigation. Reads the finding, locks context to the implicated files, and writes a regression test before the patch. No full planning phase.
/slashforge-resumeResumes an interrupted run from its last checkpoint. Verifies the git HEAD still matches, then re-enters the workflow at the next phase instead of starting over.
/slashforge-review-prReviews a pull request against your repo's own rules and conventions plus a security audit, then posts line-level comments or approves. Never posts without showing you the exact text.
/slashforge-testGenerates spec-based test coverage for existing files. A light, standalone flow: discovers your framework, writes tests, runs them, and reports — surfacing bugs without touching production code. No branch, no PR.
/slashforge-refactorRefactors with a zero-functional-change guarantee, gated by your test suite passing with identical results before and after. Auto-builds a test net first when coverage is thin.
Names follow the agent picked in the header. Codex invokes them with $ rather than /. All eight run on every agent — setup writes each host's own layout, so on Cursor you get .cursor/rules/*.mdc and on Codex nested AGENTS.md plus .codex/agents/*.toml, never .claude/.
What it costs
Tokens per runTen phases, four gates, agent code review. A multi-layer feature lands near the top.
The same run, indexed. The graph shaves roughly 4–10%; it does not change the order of magnitude.
Skips brainstorming and the review agent. Every user gate and all verification stay.
No code is written, so this is reading — however far the trail runs before the cause.
Almost entirely the diff. Three files is about 2k of it; fourteen is about 42k.
Discovers your framework, writes and runs spec-based tests for the targeted files, then reports. No branch, no PR.
Zero functional change, gated by the suite passing with identical results before and after.
The range is driven by the size of the work, not by the tooling. SlashForge is deliberately heavy — if you want a prompt turned into a patch as fast as possible, this is the wrong tool.
Steering Committee
Review and feedbackPractitioners who run SlashForge on real work and shape it with their feedback.
Built to make disciplined engineering the default, not an afterthought.
Read the introduction