AI Agent Skill HUB

workflow-bug-fix

Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.

13 stars
byNickCrew
View on GitHubInstallation ↓

Best use case

workflow-bug-fix is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.

Teams using workflow-bug-fix should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/workflow-bug-fix/SKILL.md --create-dirs "https://raw.githubusercontent.com/NickCrew/Claude-Cortex/main/skills/workflow-bug-fix/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/workflow-bug-fix/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How workflow-bug-fix Compares

Feature / Agentworkflow-bug-fixStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Systematic approach to identifying, fixing, and validating bug fixes. Use when fixing bugs, resolving issues, or addressing errors.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# 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

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.