SlashForge

Workflow slash commands for AI coding agents.

Guardrails, not autocomplete.

Install
$ npx slashforge

Supports Claude Code today. Cursor and Codex targets are planned.

Node 16+MITv4.4.3

Two runs, start to finish

Shipping a feature

feat/rate-limitingcomplete
$ /slashforge:code
> add rate limiting to the public API
PHASE 2 · PLAN
rateLimit.ts new — token bucket, Redis-backed
server.ts mount before route handlers
RISKS a Redis outage would fail open
TESTS refill · boundary 100 · per-key isolation
PHASE 3 · CONFIRM — stops and waits for you
> proceed
PHASE 6 · VERIFY
lint ✓ tests ✓ build ✓
PHASE 7 · REVIEW
code-reviewer · matches the plan · 0 blocking
PHASE 8 · PR opened against main
Nothing shipped that was not planned, gated, verified.

Reviewing someone else's

reviewing #42complete
$ /slashforge:review-pr
AWAITING YOUR REVIEW
1. #42 Add retry to upload queue +180 −24 (6 files)
2. #47 Bump astro to 7.2 +12 −12 (2 files)
> 1
CONTEXT
CI green · 2 existing comments · author is not you
FINDINGS · against CLAUDE.md and .claude/rules/
blocking retry.ts:38 no cap, retries forever
should fix retry.ts:52 swallows the abort signal
nit retry.ts:12 name says ms, value is s
GATE · nothing is posted yet
approve · comment · request-changes · edit · cancel
> request-changes
POSTED · 3 line comments on #42
You saw the exact text before it went out.

What it costs

Tokens per run
Repo setup
50–120k

Once per repo, before anything else. The largest fixed load of any command, then it writes your .claude/.

Full run
100–250k

Ten phases, four gates, agent code review. A multi-layer feature lands near the top.

With Graphify
75–225k

The same run, indexed. The graph shaves roughly 4–10%; it does not change the order of magnitude.

Lean mode (-quick)
40–70k

Skips brainstorming and the review agent. Every user gate and all verification stay.

Investigating a bug
15–60k

No code is written, so this is reading — however far the trail runs before the cause.

Reviewing a PR
15–70k

Almost entirely the diff. Three files is about 2k of it; fourteen is about 42k.

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.

It empowers people to do their finest work every single time.

Read the introduction