All notable changes to this project are documented here. Format based on Keep a Changelog; this project adheres to Semantic Versioning.
[Unreleased]
Section titled “[Unreleased]”[4.0.1] - 2026-08-01
Section titled “[4.0.1] - 2026-08-01”homepagefield pointing at the documentation site. Without it npm falls back to<repository>#readme, so the package page linked to the GitHub README rather than the docs.
[4.0.0] - 2026-08-01
Section titled “[4.0.0] - 2026-08-01”Changed
Section titled “Changed”-
BREAKING: the command namespace moved from
/forge:to/slashforge:.v3 v4 /forge:setup/slashforge:setup/forge:code/slashforge:code/forge:code -quick/slashforge:code -quick/forge:investigate/slashforge:investigateforgeis a common word and was liable to collide with other tools’ commands — the exact problem namespacing was introduced to solve in v3.0.0.slashforgematches the package name. -
Command files now install into
~/.claude/commands/slashforge/instead of~/.claude/commands/forge/.
uninstallandstatusrecognise the v3forge/namespace alongside the v2 layout, so an upgrade can still be cleaned up rather than orphaned.- Migration guide for v3 → v4 in the docs.
Unchanged
Section titled “Unchanged”- The three commands, the ten phases, every user gate, and the
-quickmode all behave exactly as in v3.0.0. Guide filenames and the guides directory are untouched.
[3.0.0] - 2026-07-31
Section titled “[3.0.0] - 2026-07-31”Changed
Section titled “Changed”-
BREAKING: commands are renamed and namespaced under
/forge:.v2 v3 /setup-claude/forge:setup/code/forge:code/quick/forge:code -quick/investigate/forge:investigate/setup-claudewas tied to a single vendor, which does not survive the planned Cursor and Codex support. Theforge/namespace also stops/codecolliding with commands users already have. -
BREAKING:
/quickis no longer a separate command. It is now lean mode on/forge:code, selected with-quick. The two were never separate workflows —/quickwas always a set of overrides on the same ten phases — so they are now one command and one override guide. -
BREAKING: guide files renamed
claude-setup-*.md→forge-*.md, and the install directory moved from~/.claude/setup/claude-setup/to~/.claude/setup/slashforge/. -
Command files now install into
~/.claude/commands/forge/, which is what produces the/forge:prefix.
forge-workflow-quick.md— the lean-mode overrides, extracted from the oldquick.md. Loaded only when-quickis passed, so full mode is unaffected by it.- Install now reports any v2 files left on disk after an upgrade, rather than silently orphaning them. It does not delete them.
uninstallandstatusrecognise the v2 layout, so an upgraded install can still be cleaned up.
Removed
Section titled “Removed”- BREAKING: the
claude-setup-kitbinary alias, deprecated in v2.0.0. - BREAKING: the
CLAUDE_SETUP_KIT_YESenv var, deprecated in v2.0.0. UseSLASHFORGE_YES.
[2.0.0] - 2026-07-31
Section titled “[2.0.0] - 2026-07-31”Changed
Section titled “Changed”- BREAKING: the package is now published as
slashforge(previouslyclaude-setup-kit). Install withnpx slashforge. Renamed ahead of planned Cursor and Codex support, so the name is not tied to a single vendor. - Repository moved to
github.com/rajdeepratan/SlashForge; the old URL permanently redirects. - Non-interactive mode is now enabled by
SLASHFORGE_YES=1. - Expanded npm keywords and GitHub topics for discoverability.
Deprecated
Section titled “Deprecated”- The
claude-setup-kitnpm package. Useslashforgeinstead. - The
claude-setup-kitbin alias andCLAUDE_SETUP_KIT_YES=1env var. Both still work so existing scripts and CI do not break, and are scheduled for removal in v3.0.0.
- Auto-release now publishes to npm. A release created by
GITHUB_TOKENdoes not trigger other workflows, sopublish.ymlnever fired;auto-release.ymlnow dispatches it explicitly viaworkflow_dispatch.
[1.5.0] - 2026-07-02
Section titled “[1.5.0] - 2026-07-02”- Test suite (
node:test) and a CI workflow running on push/PR across Node 18/20/22. - Auto-release workflow: a version bump merged to
maincreates the matching tag + GitHub Release, which triggers publishing. - npm provenance on publish, with a test gate before
npm publish. uninstallsubcommand to remove the kit’s guides and commands.--projectinstall mode: vendors guides + commands into a repo’s./.claude/(repo-relative paths) so a cloned repo gets working commands with no global install..gitignoreand this changelog.
[1.4.0] - 2026-06-28
Section titled “[1.4.0] - 2026-06-28”Changed
Section titled “Changed”/setup-clauderestructured into five phases so all user decisions are batched up front; only Graphify’sCLAUDE.mdappend runs last, preserving the “kit’s CLAUDE.md first” ordering.
[1.3.0] - 2026-05-16
Section titled “[1.3.0] - 2026-05-16”- Self-contained
SUMMARY.htmlsynthesis and investigation findings as HTML.
[1.2.1] - 2026-05-05
Section titled “[1.2.1] - 2026-05-05”- Graphify offer no longer short-circuits when the CLI is already on
PATH.
[1.2.0] - 2026-05-01
Section titled “[1.2.0] - 2026-05-01”- Preflight checks,
/quickcommand, Graphify integration, graph-freshness check, and.claude/coverage detection.