mcpField
W
workflow-bug-fix

workflow-bug-fix

github.com/nickcrewDevelopment6238 installsUpdated 17w ago
Repository

About workflow-bug-fix

workflow-bug-fix is a systematic bug-fixing process for development teams, covering work from root-cause analysis through deployment validation. It includes a minimal-scope fix, code review, regression testing, security checks, documentation, and post-deployment monitoring.

Key features

  1. 01Reproduce issues and analyze root causes
  2. 02Implement minimal, compatible fixes
  3. 03Review correctness, side effects, and edge cases
  4. 04Add regression and edge-case tests
  5. 05Run security checks and post-deployment monitoring

Use cases

  1. 01Trace logs and errors to find root causes
  2. 02Add regression tests for bug fixes
  3. 03Check fixes for newly introduced security issues
  4. 04Plan hotfixes and monitoring for critical bugs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill workflow-bug-fix

After installing, type/workflow-bug-fixin Claude Code to confirm it loaded.

Details

From the project README

Bug Fix Workflow

Systematic process for fixing bugs properly.

Phase 1: Root Cause Analysis

Agents: root-cause-analyst

Methods:

  • Error trace analysis
  • Log investigation
  • State inspection
  • Reproduce the bug consistently

Output: Root cause, affected components, impact assessment

Phase 2: Fix Implementation

Constraints:

  • Minimal scope (fix the bug, nothing more)
  • Backward compatible
  • Well tested

Phase 3: Code Review

Agents: code-reviewer

Focus:

  • Fix correctness
  • Side effects
  • Edge cases

Phase 4: Regression Testing

Agents: test-automator

Create tests:

  • Regression test (prevents this bug from returning)
  • Edge case tests
  • Integration tests if affected

Phase 5: Security Check

Agents: security-auditor

Blocking: Ensure fix doesn't introduce vulnerabilities

Phase 6: Validation

Agents: quality-engineer

Checklist:

  • Original issue resolved
  • No new issues introduced
  • All tests pass

Phase 7: Documentation

Agents: technical-writer

  • Changelog entry
  • Incident report (for significant bugs)
  • Prevention guide (what caused it, how to avoid)

Phase 8: Deployment

Agents: deployment-engineer

Strategy: Hotfix if critical, normal release otherwise

Monitor for 24h:

  • Error rate
  • Performance metrics
  • User reports

Success Criteria

  • Bug verified fixed
  • Regression tests added
  • No side effects
  • Documentation updated

Anti-patterns

  • ❌ Fixing symptoms instead of root cause
  • ❌ Large scope changes mixed with bug fix
  • ❌ Skipping regression tests
  • ❌ No documentation of what caused it

Comments

Markdown supported