Use Case: Verification & Build

Scenario 1: Fixing Build Errors

Profile: Junior Developer, build fails after making changes

Step 1: Fix the build

“The build is failing with 12 type errors.”

Tool: /build-fix (command) invokes build-error-resolver agent (Sonnet)

Input	Build/type error output from terminal
Output	Minimal fixes: type annotations, null checks, import fixes. Strictly NO refactoring.

What it will do:

• Add missing type annotations
• Add null checks where needed
• Fix broken imports
• Update type definitions

What it will NOT do:

• Refactor code
• Change architecture
• Rename variables
• Add features

---

Scenario 2: Pre-Merge Verification

Profile: Senior Developer, running final checks before creating a PR

Step 1: Full verification loop

“Run all checks before I submit this PR.”

Tool: verification-loop skill guides a 6-phase check

Phase	Check	What it catches
1	Build	Compilation errors
2	Type check	Type safety issues
3	Lint	Style violations
4	Tests	Logic errors, regressions
5	Security scan	Vulnerabilities
6	Diff review	Unintended changes

Input	Codebase in its current state
Output	Pass/fail report for each phase with specific issues to fix

---

Scenario 3: AI Regression Testing

Profile: QA Lead, ensuring AI-generated changes don’t break things

Step 1: Set up regression guards

“How do I prevent AI-generated code from breaking existing functionality?”

Tool: ai-regression-testing skill

Input	AI-assisted codebase with regression concerns
Output	Strategy for snapshot tests, integration tests, and change impact analysis

---

Verification Tool Comparison

Tool	Scope	When to use	Approach
/build-fix	Single error fix	Build just broke	Minimal, one-at-a-time fixes
verification-loop	Full pre-merge check	Before PR	6-phase comprehensive scan
ai-regression-testing	Regression prevention	After AI changes	Testing strategy guidance