Skip to content
learn
Global menu

SlashForge, workflow commands for Claude Code — Mission

Why I’m learning this

Section titled “Why I’m learning this”

The agentic coding course taught the pieces Claude Code gives you: project instructions, commands, skills, subagents, hooks. It did not show what a complete workflow built from those pieces looks like. SlashForge is one: four commands and nine skills that take a request through intake, plan, confirmation, branch, implementation, verification, review, pull request, feedback and cleanup, and stop at four gates where nothing continues until you answer.

It is a good specimen for two reasons. It is small enough to read — one 676-line installer and twenty-nine Markdown templates — and it is honest about its cost: its README says it is “deliberately heavy” and gives token budgets for each command. And every behaviour it has lives in plain text you can open, which means you can check each claim it makes against the file that is supposed to implement it.

That is what this course does. It installs SlashForge where it can do no harm, reads what it wrote, and compares the documentation, the installer and Claude Code’s own rules with each other. They don’t always agree: the QA table of the journal lists where.

Who this course is for

Section titled “Who this course is for”

You write C# or Java, you have used Claude Code — the agentic coding course up to its lesson 3 is enough — and you want to know what an opinionated workflow kit adds, what it costs and what it installs on your machine before you run it. You don’t need to know JavaScript: the installer is read, not written.

A workflow kit, in .NET and Java terms

Section titled “A workflow kit, in .NET and Java terms”
.NET / Java SlashForge
Distribution a NuGet or Maven package an npm package, run once with npx
What it installs assemblies, templates (dotnet new install) Markdown files under ~/.claude/ or ./.claude/
The executable part compiled code a 676-line installer; the rest is text that Claude Code reads
How you invoke it a CLI verb, an IDE command a slash command: /slashforge:code
Guard rails branch policies, required reviews four gates written into the instructions — the model is told to stop
Configuration appsettings.json, pom.xml your repository’s CLAUDE.md and .claude/rules/

The last two rows are the ones to keep in mind. A branch policy is enforced by the server; a SlashForge gate is a sentence the model is asked to obey. The agentic coding course draws the same line between instructions and hooks.

By the end of this course, I will be able to

Section titled “By the end of this course, I will be able to”
  • install SlashForge globally or into one repository without touching the rest of ~/.claude/, and remove it cleanly;
  • say, for each file it writes, what Claude Code does with it and why its path matters;
  • read a command file and follow it into the guides it delegates to;
  • run /slashforge:setup, /slashforge:code and its -quick mode, /slashforge:investigate and /slashforge:review-pr on a real repository, and measure what they cost;
  • decide, for a given change, whether the ceremony is worth it.

Outline

Section titled “Outline”
# Lesson You already know
1 What the installer writes dotnet tool install, dotnet new install, a package that drops files
2 Inside the files: commands, skills, guides template parameters, routing by folder, a validator that is stricter than the runtime
3 /slashforge:setup against /init a project template, an onboarding checklist
4 /slashforge:code: ten phases and four gates branch policies, a pull request template
5 /slashforge:investigate and /slashforge:review-pr a hotfix process, a bug report, a code review
6 Making it yours: rules, verification, a team install .editorconfig, a shared build configuration
7 Contributing back: from a finding to a verified fix a bug report, a release note, a regression test
— Journal

Resources

Section titled “Resources”