bugfix-workflow

Original：🇨🇳 Chinese

Translated

General Bugfix Workflow Knowledge Base, including TDD process, output format specifications, confidence scoring standards, and general best practices. Applicable to all tech stacks (backend/frontend/e2e).

1installs

Sourcepenkzhou/swiss-army-knife-plugin

Added on2026-02-10

NPX Install

npx skill4agent add penkzhou/swiss-army-knife-plugin bugfix-workflow

SKILL.md Content (Chinese)

View Translation Comparison →

General Bugfix Workflow Knowledge Base

This Skill provides general knowledge of the standardized 6-phase Bugfix workflow, applicable to all tech stacks.

TDD Process (Core Principles)

RED Phase (Write failing tests first)

Tests must reproduce the current bug
Tests must fail before the fix
Tests should verify behavior, not implementation

Verification command template:

bash

make test TARGET={stack} FILTER={test_file}

GREEN Phase (Minimal implementation)

Only write the minimal code required to pass the tests
Do not optimize during this phase
Do not add features not covered by tests

REFACTOR Phase (Refactoring)

Improve code structure
Keep tests passing
Eliminate duplicate code

Final verification:

bash

make test TARGET={stack}
make lint TARGET={stack}
make typecheck TARGET={stack}

Confidence Scoring Standards

Root Cause Analysis Confidence

Score Range	Action
≥60	Proceed automatically
40-59	Pause and ask user
<40	Stop and collect more information

Code Review Confidence

Score Range	Level	Action
≥90	Critical	Auto-fix
80-89	Important	Auto-fix
<80	Below threshold	Do not report

General Output Format

Error Structure

json

{
  "id": "BF-{YYYY}-{MMDD}-{NNN}",
  "file": "File path",
  "line": Line number,
  "severity": "critical|high|medium|low",
  "category": "Error type",
  "description": "Issue description",
  "evidence": ["Evidence supporting the judgment"],
  "stack": "Stack trace"
}

Summary Structure

json

{
  "total": Total count,
  "by_type": { "Type": Count },
  "by_file": { "File": Count }
}

Solution Structure

json

{
  "solution": {
    "approach": "Overview of fix思路",
    "steps": ["Step 1", "Step 2"],
    "risks": ["Risk 1", "Risk 2"],
    "estimated_complexity": "low|medium|high"
  },
  "tdd_plan": {
    "red_phase": { "tests": [...] },
    "green_phase": { "changes": [...] },
    "refactor_phase": { "items": [...] }
  },
  "impact_analysis": {
    "affected_files": [...],
    "api_changes": [...],
    "test_impact": [...]
  },
  "security_review": {
    "performed": true/false,
    "vulnerabilities": [...],
    "passed": true/false
  }
}

Execution Result Structure

json

{
  "issue_id": "BF-2025-MMDD-001",
  "phases": {
    "red": { "status": "pass|fail|skip", "duration_ms": 1234 },
    "green": { "status": "pass|fail|skip", "changes": [...] },
    "refactor": { "status": "pass|fail|skip", "changes": [...] }
  },
  "overall_status": "success|partial|failed"
}

Impact Analysis Dimensions

Direct Impact: Modified files
Indirect Impact: Components dependent on modified files
API Impact: Whether there are breaking changes
Test Impact: Tests that need to be updated

Security Review Checklist (Common Security Issues)

Perform only when involving sensitive code (authentication, input handling, data storage, etc.):

SQL/Command injection
XSS Cross-site scripting
Sensitive information leakage
Authentication/Authorization issues
Insufficient input validation

Batch Execution Strategy

Default batch size: 3 issues per batch
After each batch completion: Output batch report and wait for user confirmation
Failure handling: Record failure reason, retry up to 3 times, mark as failed after 3 failures

Bugfix Documentation Template

markdown

# [Issue Brief] Bugfix Report

> Date: {YYYY-MM-DD}
> Confidence: {confidence}/100
> Tech stack: {stack}

## 1. Issue Description

### 1.1 Error Messages
[Structured error list]

### 1.2 Root Cause Analysis
[Root cause description + evidence]

## 2. Fix Solution

### 2.1 TDD Plan

#### RED Phase
[Failing test code]

#### GREEN Phase
[Minimal implementation code]

#### REFACTOR Phase
- [ ] Refactoring items

### 2.2 Impact Analysis
[Impact scope]

## 3. Verification Plan

- [ ] Tests passed
- [ ] Coverage meets standard
- [ ] No regression

Knowledge Precipitation Standards

Knowledge Worth Precipitating

Newly discovered issue patterns - Error types not documented before
Reusable solutions - Fix patterns applicable to multiple scenarios
Important lessons - Common mistakes, counterintuitive behaviors
Performance optimization - Test execution speed improvements

Cases Not Needing Precipitation

One-time issues - Typos specific to a single file
Already covered by existing documentation - Issue already recorded in troubleshooting

Quality Gate Standards

Check Item	Standard	Blocking Level
Test Pass Rate	100%	Blocking
Coverage	>= 90%	Blocking
New Code Coverage	100%	Blocking
Lint	No errors	Blocking
TypeCheck	No errors	Blocking
Regression Test	No regression	Blocking

bugfix-workflow

NPX Install

Tags

SKILL.md Content (Chinese)

General Bugfix Workflow Knowledge Base

TDD Process (Core Principles)

RED Phase (Write failing tests first)

GREEN Phase (Minimal implementation)

REFACTOR Phase (Refactoring)

Confidence Scoring Standards

Root Cause Analysis Confidence

Code Review Confidence

General Output Format

Error Structure

Summary Structure

Solution Structure

Execution Result Structure

Impact Analysis Dimensions

Security Review Checklist (Common Security Issues)

Batch Execution Strategy

Bugfix Documentation Template

Knowledge Precipitation Standards

Knowledge Worth Precipitating

Cases Not Needing Precipitation

Quality Gate Standards