Kits
EngineerKit
25 commands, 4 skills, and 4 read-only agents for professional software engineering with Claude Code — every command ends with evidence, never a bare "done".
EngineerKit is a full SDLC harness for Claude Code: planning, TDD, root-cause debugging, fresh-context reviews, security sweeps, and releases — where every command ends with evidence (test output, diffs, exit codes), never a bare "done".
| Commands | 25 (/eng-*) |
| Skills | 4 |
| Agents | 4 |
| Measured footprint | 20,413 tokens |
Who it's for
Staff engineers, founding engineers, and platform teams who already live in Claude Code and want it to behave like a disciplined senior, not an eager intern. The kit's spine is the daily-8 loop — /eng-catchup, /eng-plan, /eng-tdd, /eng-debug, /eng-verify, /eng-review, /eng-commit, /eng-handoff — the commands you actually run every day.
Shared context
The eng-context skill defines how the kit keeps memory across sessions: CLAUDE.md guardrails (grown by /eng-learn every time you correct a mistake), a docs/MAP.md codebase map built by /eng-onboard, and a .claude/handoff.md continuation file written by /eng-handoff so the next session picks up without re-explaining.
Commands
| Command | What it does |
|---|---|
/eng-catchup | Get back up to speed after a /clear, a pull, or a day away — reads what changed so you don't re-explain. |
/eng-commit | Commit your staged work with a clean conventional message — refuses if tests fail or secrets are in the diff. |
/eng-debug | Find the actual root cause before touching code — evidence, ranked hypotheses, minimal fix, regression test. |
/eng-docs | Sync README, API docs, and changelog with what the code actually does now — driven by the real diff. |
/eng-fix-ci | Pull the failing CI logs, find the real failure, fix it, push, and watch until the checks go green. |
/eng-fix-issue | Take a GitHub issue from number to merged-ready PR: reproduce, fix at the root, test, ship. |
/eng-handoff | Write a continuation file before you stop — the next session picks up without re-explaining. |
/eng-hooks | Interview you about what keeps going wrong, then install hooks that make it impossible — not just discouraged. |
/eng-interview | Get interviewed about what you want to build until the requirements are nailed, then get a complete SPEC.md. |
/eng-learn | Turn a mistake or correction into a CLAUDE.md guardrail so it never happens twice — the compounding move. |
/eng-migrate | Run a mechanical migration safely: prove the transform on 2–3 files first, then fan out batch by verified batch. |
/eng-onboard | Map an unfamiliar codebase — stack, entry points, how to run it — into a docs/MAP.md you reuse every session. |
/eng-plan | Explore the code, propose an approach with file list and risks — and wait for your go before touching anything. |
/eng-pr-review | Review someone else's PR: pull it, run it, structured findings with file:line — ready to paste or post. |
/eng-refactor | Restructure code safely — characterization tests first, one concern per step, suite green between every step. |
/eng-release | Cut a release: version bump, changelog from merged PRs, tag, and publishable release notes — all verified. |
/eng-review | Fresh-context review of your diff — flags only what would block a merge, with a confidence level per finding. |
/eng-security | Security scan of your diff — injection, auth gaps, secrets, SSRF — each finding with severity and the fix. |
/eng-ship | Commit, push, and open a PR with a description generated from the actual diff — one command, branch to PR. |
/eng-simplify | Strip the over-engineering out of a change — dead abstractions, premature generality, code that does nothing. |
/eng-spec | Turn SPEC.md into phased, verifiable tasks — each phase ends with a check that proves it landed. |
/eng-tdd | Build a feature test-first: failing test shown red, minimal code to green, refactor only on green. |
/eng-test-gaps | Find the tests that can't fail and the cases nobody tests — silent failures, mock-heavy lies, missing edges. |
/eng-verify | Actually run it — tests, build, the app itself — and show the output proving the change works. |
/eng-worktree | Spin up a git worktree with its own branch so a second task runs in parallel without touching this one. |
/eng-debug "login redirects to /404 after the auth refactor"Skills & agents
Skills: eng-context (session memory), eng-debugging (the root-cause protocol), eng-git (the commands that destroy work, worktree workflow), eng-testing (what makes a test trustworthy). Agents — all read-only: code-reviewer, explorer, security-auditor, test-auditor.
Install
ck install engineerkit
ck tokens engineerkitLearn more
- See the full command explorer, token ledger, and flagship demo on the EngineerKit page.