Menü
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | fix-bug |
| description | Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages. |
| user-invocable | true |
| allowed-tools | ["Read","Skill","Task"] |
| version | 1.0.0 |
| author | Ashay Kubal @ Qball Inc. |
This skill triggers the Fix Validation pipeline to systematically investigate, fix, and validate a bug.
Load this skill when the user request matches ANY of these patterns:
| Trigger Pattern | Example User Request |
|---|---|
| Bug fix requests | "Fix this bug", "Something is broken in X" |
| Error investigation | "Users report errors in X", "This feature isn't working" |
| Regression fixes | "This used to work", "Breaking after recent changes" |
| Production issues | "Login fails for new accounts", "API returns 500" |
| Flaky behavior | "Tests pass sometimes", "Intermittent failures" |
DO NOT use this skill for:
| Anti-Pattern | Use Instead |
|---|---|
| Ad-hoc fixes without investigation | Direct fix (skip pipeline) |
| Simple typo corrections | Direct edit |
| Refactoring without reported issues | Code Review pipeline |
| Adding new features | New Feature pipeline |
| Performance optimization | Research & Planning pipeline |
Without this skill, conversational prompts like "please investigate and fix this bug" may cause Claude to skip pipeline stages and fix directly. This skill ensures deterministic execution of all Fix Validation pipeline stages.
/fix-bug <path> [description]
Arguments:
$1 (required): Path to code with the bug$2 and beyond (optional): Description of the issue - recommended for better analysisExamples:
/fix-bug src/auth/login.ts "Users report login fails for new accounts"
/fix-bug tests/fixtures/fix-validator/simple-fix/ "Cannot read property displayName of undefined"
/fix-bug src/api/routes.ts
When invoked, follow the Fix Validation pipeline exactly:
IssueAnalyzer (bulwark-issue-analyzer) // Sonnet - root cause analysis
|> FixWriter (bulwark-implementer) // Opus - implement fix
|> (if !tests_cover_scenario // Conditional: only if tests don't already exist
then TestWriter |> TestAudit // Opus writes, then audit for T1-T4
else Skip)
|> FixValidator (bulwark-fix-validator) // Sonnet - validate against debug report
|> CodeReviewer (general-purpose) // Sonnet - review fix
|> (if !approved
then IssueAnalyzer // Loop back
else Done)
|> LOOP(max=3) // Max 3 iterations
MUST spawn bulwark-issue-analyzer agent via Task tool:
Task(
subagent_type="bulwark-issue-analyzer",
model="sonnet",
prompt="GOAL: Analyze the bug and produce a debug report..."
)
Input: Path from $1, description from $2 onward
Output: Debug report at logs/debug-reports/{issue-id}-{timestamp}.yaml
Do NOT skip this stage. The debug report is required for subsequent stages.
MUST spawn bulwark-implementer agent via Task tool:
Task(
subagent_type="bulwark-implementer",
prompt="GOAL: Fix the identified issue based on the debug report.
CONSTRAINTS: Only fix the identified issue. Write tests for the fix. Max 3 quality gate retries.
CONTEXT:
mode: fix
debug_report_path: logs/debug-reports/{issue-id}-{timestamp}.yaml
root_cause: {from Stage 1}
affected_files: {from Stage 1}
fix_approach: {from Stage 1}
OUTPUT: Implementation report at logs/implementer-{id}-{timestamp}.yaml"
)
Input: Debug report from Stage 1
Output: Implementation report at logs/implementer-{id}-{timestamp}.yaml
SA6 Note: The implementer returns pipeline suggestions with MANDATORY language in its summary. Evaluate each suggestion per SA6.
Do NOT implement the fix yourself. The implementer agent handles quality gates and structured output.
Condition: Check debug report's validation_plan.recommendation.new_tests_needed
If tests needed:
If tests exist: Skip to Stage 3b or Stage 4
Condition: Run if any test files were created or modified in Stage 2 (FixWriter) OR Stage 3 (TestWriter). This ensures implementer-written tests receive T1-T4 audit even when TestWriter is skipped.
Action: Run mock-detection on new/modified tests to verify T1-T4 compliance
If T1 violation: Return to TestWriter (or FixWriter if TestWriter was skipped), request rewrite
If T2-T4 violations: Log warning, proceed
MUST spawn bulwark-fix-validator agent via Task tool:
Task(
subagent_type="bulwark-fix-validator",
model="sonnet",
prompt="GOAL: Validate the fix against the debug report...
CONTEXT:
Debug Report: logs/debug-reports/{issue-id}-{timestamp}.yaml
Fix Applied: {description of changes}
Tests Added: {if any}
..."
)
Input: Debug report path, fix details, test details
Output: Validation report at logs/validations/fix-validation-{issue-id}-{timestamp}.yaml
MUST spawn general-purpose agent via Task tool:
Task(
subagent_type="general-purpose",
model="sonnet",
prompt="GOAL: Review the fix for correctness, completeness, and safety.
CONSTRAINTS: Do NOT modify any files. Review only.
CONTEXT:
debug_report: logs/debug-reports/{issue-id}-{timestamp}.yaml
fix_applied: {description of changes from Stage 2}
tests_added: {from Stage 3, if any}
validation_results: {from Stage 4}
OUTPUT: Approval decision (approved: true/false) with concerns and recommendations."
)
Approval Criteria:
If rejected and iterations < 3:
If rejected and iterations >= 3:
After each stage, report progress to user:
Stage 1 (IssueAnalyzer): Complete
- Debug report: logs/debug-reports/AUTH-001-20260120.yaml
- Root cause: {summary}
- Complexity: {low|medium|high}
Stage 2 (FixWriter): Complete
- Files modified: {list}
- Fix: {brief description}
Stage 3 (TestWriter): {Complete|Skipped}
- Tests added: {count or "existing tests sufficient"}
Stage 4 (FixValidator): Complete
- Confidence: {HIGH|MEDIUM|LOW}
- Recommendation: {proceed|revise}
Stage 5 (CodeReviewer): Complete
- Decision: {Approved|Rejected}
| Error | Action |
|---|---|
| IssueAnalyzer fails to identify root cause | Report to user, ask for more context |
| Tests cannot be executed | FixValidator uses manual validation strategy |
| FixValidator confidence is LOW | Escalate to user with details |
| Max iterations reached | Summarize attempts, ask user for guidance |
| Resource | Location |
|---|---|
| Pipeline definition | pipeline-templates/references/fix-validation.md |
| IssueAnalyzer agent | agents/bulwark-issue-analyzer.md |
| Implementer agent | agents/bulwark-implementer.md |
| FixValidator agent | agents/bulwark-fix-validator.md |
| Issue debugging skill | issue-debugging/SKILL.md |
Note: Paths are relative to your skills/agents directory (either skills/ or .claude/skills/).
Validates Claude Code assets (skills, hooks, agents, commands, MCP servers, plugins) against official Anthropic standards. Fetches latest docs dynamically and produces structured validation reports.
Real output verification vs mock calls. Use when transforming T1-T4 violating tests to verify observable behavior.
Curated edge case test data for boundary testing, verification scripts, and test generation. Provides pre-curated reference data organized by data type with context-specific loading guidance.
Role-based brainstorming with dual modes: --scoped (sequential Task tool, 5 roles) and --exploratory (Agent Teams peer debate, 4 roles). Use for feasibility assessment and idea validation.
Structured multi-viewpoint research using 5 parallel Sonnet sub-agents. Use when deep research is needed on a complex topic before implementation planning.
Initialize Bulwark infrastructure in a project: language-aware Justfile (8 langs), bun + eval-framework toolchain, logs/ subdirectories, and optional hooks.