Skip to content

Changelog

Release history for SlashForge.

All notable changes to this project are documented here. Format based on Keep a Changelog; this project adheres to Semantic Versioning.

  • homepage field 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.
  • 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:investigate

    forge is a common word and was liable to collide with other tools’ commands — the exact problem namespacing was introduced to solve in v3.0.0. slashforge matches the package name.

  • Command files now install into ~/.claude/commands/slashforge/ instead of ~/.claude/commands/forge/.

  • uninstall and status recognise the v3 forge/ namespace alongside the v2 layout, so an upgrade can still be cleaned up rather than orphaned.
  • Migration guide for v3 → v4 in the docs.
  • The three commands, the ten phases, every user gate, and the -quick mode all behave exactly as in v3.0.0. Guide filenames and the guides directory are untouched.
  • 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-claude was tied to a single vendor, which does not survive the planned Cursor and Codex support. The forge/ namespace also stops /code colliding with commands users already have.

  • BREAKING: /quick is no longer a separate command. It is now lean mode on /forge:code, selected with -quick. The two were never separate workflows — /quick was 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-*.mdforge-*.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 old quick.md. Loaded only when -quick is 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.
  • uninstall and status recognise the v2 layout, so an upgraded install can still be cleaned up.
  • BREAKING: the claude-setup-kit binary alias, deprecated in v2.0.0.
  • BREAKING: the CLAUDE_SETUP_KIT_YES env var, deprecated in v2.0.0. Use SLASHFORGE_YES.
  • BREAKING: the package is now published as slashforge (previously claude-setup-kit). Install with npx 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.
  • The claude-setup-kit npm package. Use slashforge instead.
  • The claude-setup-kit bin alias and CLAUDE_SETUP_KIT_YES=1 env 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_TOKEN does not trigger other workflows, so publish.yml never fired; auto-release.yml now dispatches it explicitly via workflow_dispatch.
  • 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 main creates the matching tag + GitHub Release, which triggers publishing.
  • npm provenance on publish, with a test gate before npm publish.
  • uninstall subcommand to remove the kit’s guides and commands.
  • --project install mode: vendors guides + commands into a repo’s ./.claude/ (repo-relative paths) so a cloned repo gets working commands with no global install.
  • .gitignore and this changelog.
  • /setup-claude restructured into five phases so all user decisions are batched up front; only Graphify’s CLAUDE.md append runs last, preserving the “kit’s CLAUDE.md first” ordering.
  • Self-contained SUMMARY.html synthesis and investigation findings as HTML.
  • Graphify offer no longer short-circuits when the CLI is already on PATH.
  • Preflight checks, /quick command, Graphify integration, graph-freshness check, and .claude/ coverage detection.