Troubleshooting

The handful of things that actually go wrong, and what to do about each.

The commands do not appear

By far the most common one. You type / in Claude Code and see nothing named slashforge.

It installed an old version

npx slashforge printed a version older than the one on npm, and commands you expected are missing.

npx prefers an executable already on your PATH. If npm install -g slashforge was ever run, npx slashforge runs that copy and never contacts the registry, so it keeps installing the old release while reporting success.

which slashforge          # a path here is the problem
npm uninstall -g slashforge
npx slashforge            # now resolves the current release

Keep the global install instead if you prefer — npm install -g slashforge@latest updates it in place. Either way npx slashforge status will tell you whether the copy you just ran is current.

A phase is being skipped

Usually one of two things, and both are working as designed.

• /slashforge:code classified the task as trivial. Phase 1 auto-detects small changes and skips brainstorming. Say full flow to override. See Skills for what runs at each phase.
• -quick is doing what it says. Lean mode skips brainstorming and swaps the agent code review for an inline checklist. Every user gate and all verification stay.

Setup will not overwrite a file

That is the generated_by marker working. A file whose marker is missing or has been edited is treated as yours, and will only ever have gaps filled — never be overwritten.

Delete the file if you genuinely want it regenerated from scratch.

Graphify is not being offered

/slashforge:setup only offers it when at least 70% of non-trivial source files are in a supported language. On YAML, shell, or config-only repos it skips silently. That is intended, not a failure — see Graphify for the supported languages.

Verification fails but the code looks right

Phase 6 runs your repo’s own lint, test, and build commands. If they pass locally but fail in the run, the usual cause is a command that depends on environment variables or services that the agent’s shell does not have. Fix the command, not the workflow — Phase 6 failing is the feature doing its job.

Still stuck

Open an issue and include the output of npx slashforge status. It is the single most useful thing you can attach.

For anything that does not belong in a public issue, email slashforge@rajdeepratan.com.