菜单
Debug and fix bugs by reproducing issues, identifying root causes, implementing fixes, and validating without regressions. Use when debugging reported bugs, investigating test failures, or resolving production issues requiring root cause analysis.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/adolfoaranaes12/BMAD-ENHANCED --skill fix-issue命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | fix-issue |
| description | Debug and fix bugs by reproducing issues, identifying root causes, implementing fixes, and validating without regressions. Use when debugging reported bugs, investigating test failures, or resolving production issues requiring root cause analysis. |
| acceptance | [{"bug_reproduced":"Bug successfully reproduced with failing test"},{"root_cause_identified":"Root cause clearly identified and documented"},{"fix_applied":"Minimal fix applied addressing root cause"},{"tests_passing":"Bug test now passes, all existing tests pass"},{"no_regressions":"No regressions introduced by fix"},{"edge_cases_tested":"Edge cases identified and tested"}] |
| inputs | {"issue_id":{"type":"string","required":true,"description":"Issue/bug identifier (e.g., bug-login-email, issue-42)","validation":"Must be valid issue identifier"},"severity":{"type":"enum","required":false,"description":"Issue severity: critical, high, medium, low","default":"medium"},"reproduction_confirmed":{"type":"boolean","required":false,"description":"Whether reproduction is confirmed","default":false}} |
| outputs | {"fix_complete":{"type":"boolean","description":"Whether bug fix is complete"},"bug_test_passes":{"type":"boolean","description":"Whether the new bug test passes"},"all_tests_pass":{"type":"boolean","description":"Whether all tests pass (no regressions)"},"regression_count":{"type":"number","description":"Number of regressions introduced (should be 0)"},"edge_case_tests_added":{"type":"number","description":"Number of edge case tests added"},"files_modified":{"type":"array","description":"List of files modified during fix"},"root_cause_location":{"type":"string","description":"File and line where root cause was identified"}} |
| telemetry | {"emit":"skill.fix-issue.completed","track":["issue_id","severity","reproduction_confirmed","root_cause_identified","duration_ms","files_modified_count","tests_added","tests_passed","regression_count"]} |
Debug and fix bugs, issues, or failing tests through systematic reproduction, root cause analysis, minimal fixes, and comprehensive validation.
Core Principle: Always write failing test first, fix with minimal changes, validate with full test suite.
Parse issue description:
Load context:
Example Analysis:
Issue: "Login fails when email contains + symbol"
Analysis:
- What: Login endpoint rejects valid emails with + symbol
- When: Always for emails like "user+tag@example.com"
- Where: POST /api/auth/login
- Expected: Email accepted, login succeeds
- Actual: Returns 400 "Invalid email format"
- Impact: Medium (blocks some users)
Create failing test that demonstrates the bug:
describe('[Bug Fix] Login with + symbol in email', () => {
it('should accept email addresses with + symbol', async () => {
await User.create({
email: 'user+tag@example.com',
password: await bcrypt.hash('SecurePass123!', 12)
});
response = (app)
.()
.({
: ,
:
});
(response.).();
(response.).();
});
});
Run test and verify it fails with expected error.
Document reproduction steps for future reference.
Trace execution path:
For the email example:
POST /api/auth/login
↓ auth.controller.ts:login()
↓ loginSchema.safeParse(req.body) ← Validation fails here
↓ z.string().email() ← Too strict, rejects + symbol
Document root cause:
**Root Cause:**
- Location: src/schemas/auth.schema.ts:5
- Issue: z.string().email() rejects valid RFC 5322 emails with + symbol
- Why wrong: + symbol is valid in email local part
- Impact: Users with + in email cannot log in
See: references/debugging-techniques.md for common debugging approaches
Make minimal change to fix the issue:
// src/schemas/auth.schema.ts
// Custom email regex that allows + symbol (RFC 5322 compliant)
const EMAIL_REGEX = /^[A-Za-z0-9._+%-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$/;
export const loginSchema = z.object({
email: z.string().regex(EMAIL_REGEX, 'Invalid email format'),
password: z.string().min(1, 'Password is required'),
});
Guidelines:
Run tests in order:
Failing test (should now pass)
npm test -- --testNamePattern="Login with \\+ symbol"
Related tests (no regressions)
npm test auth
Full test suite (no unexpected failures)
npm test
Manual testing (if applicable)
Verify:
Identify related edge cases that could have similar issues:
describe('[Bug Fix] Email validation edge cases', () => {
it('should accept email with multiple + symbols', async () => { /* ... */ });
it('should accept email with dots in local part', async () => { /* ... */ });
it('should accept email with hyphen in domain', async () => { /* ... */ });
it('should reject email without @ symbol', async () => { /* ... */ });
it('should reject email without domain extension', async () => { /* ... */ });
});
Run edge case tests and verify all pass.
Clean up:
Document fix:
Update task file with bug fix record:
## Bug Fixes
### Fix: Email validation rejects + symbol
**Date:** 2025-01-15
**Root Cause:** Zod's email() validator too strict
**Changes:** Custom RFC 5322-compliant regex
**Impact:** Users with + in email can now log in
**Tests:** 6 new tests, all passing, no regressions
**Files Changed:**
- src/schemas/auth.schema.ts (3 lines)
- src/__tests__/integration/auth.integration.test.ts (60 lines)
Commit:
git commit -m "fix: allow + symbol in email addresses
- Replaced Zod email() with RFC 5322-compliant regex
- Added test for + symbol in email
- Added 5 edge case tests
Fixes: Email validation incorrectly rejected valid emails
Tests: 6 new tests, all passing, no regressions"
✅ Bug Fixed: Email validation rejects + symbol
**Root Cause:** src/schemas/auth.schema.ts:5 - Zod email() validator too strict
**Fix:** Custom RFC 5322-compliant regex allowing + symbol
**Impact:** Users with + in email can now log in
**Validation:**
- ✅ Bug test passes
- ✅ All existing tests pass (no regressions)
- ✅ 5 edge case tests added, all pass
**Files Changed:**
- Modified: src/schemas/auth.schema.ts (+3 lines)
- Added tests: src/__tests__/integration/auth.integration.test.ts (+60 lines, 6 tests)
**Status:** Committed, task file updated, ready for review
If test doesn't fail as expected:
See: references/error-scenarios.md
If existing tests fail after fix:
See: references/error-scenarios.md
If issue has multiple contributing factors:
references/common-patterns.md - Common bug patterns and fixesreferences/debugging-techniques.md - Systematic debugging approachesreferences/error-scenarios.md - Handling complex debugging scenariosreferences/test-examples.md - Comprehensive test examplesPart of BMAD Enhanced Development Suite