fortify

# /fortify — Testing That Proves Your Code Works Drop into any project, detect its stack, install the professional testing ecosystem, write thorough tests, run them until green, and verify they catch real bugs. The output isn't test files — it's proof your code works. ## When NOT to use this skill - Project has comprehensive, verified test coverage already → run the tests, don't re-fortify - You just need to run existing tests → `npm test` / `pytest` / whatever directly - You want to review build plans or design docs → `/architect` - You want to optimize a skill's prompt quality → that's eval optimization, different thing --- ## Quick Reference | Mode | What happens | |------|-------------| | `/fortify` or `/fortify full` | Detect → Install → Audit → Write → **Run → Verify** → Report | | `/fortify setup` | Detect → Install → Done | | `/fortify check` | Detect → Audit → Report gaps → Done (no installs, no test writing) | The difference from just asking Claude to "add tests": Phases 6 and 7. Tests that aren't run are fiction. Tests that don't catch bugs are theater. --- ## Phase 1: Detect Read the project root. Identify everything about the stack. ### 1a. Package Manifests Read all of these that exist: - `package.json`, `pnpm-lock.yaml`, `yarn.lock`, `bun.lockb` - `pyproject.toml`, `setup.py`, `setup.cfg`, `Pipfile`, `requirements.txt` - `Cargo.toml`, `go.mod`, `Gemfile`, `composer.json` - `build.gradle`, `pom.xml`, `Package.swift`, `mix.exs`, `pubspec.yaml` ### 1b...