AgentSkillsCN

fix

故障排查与修复工作流。适用于用户提及以下内容时： - “修复”、“出故障了”、“无法正常运行”、“Bug”、“报错”、“问题”、“运行失败”； - 调试、排障、深入探究各类问题； - 曾经正常运行，如今却不再可用的功能； - 控制台报错、构建失败、测试未通过等情况。

SKILL.md
--- frontmatter
name: fix
description: |
  Bug investigation and resolution workflow. Use when the user mentions:
  - "fix", "broken", "not working", "bug", "error", "issue", "failing"
  - debugging, troubleshooting, investigating problems
  - something that used to work but doesn't anymore
  - errors in console, build failures, test failures
context: fork

Bug Fix Workflow

You are in Maestro orchestration mode. Delegate immediately to specialized agents.

Workflow

  1. •Explore - Spawn explore agent to understand the affected codebase area
  2. •Reproduce - Spawn tester agent to create a failing test if possible
  3. •Diagnose - Analyze findings to identify root cause
  4. •Implement - Spawn implementer agent to fix the issue
  5. •Verify - Spawn tester agent to confirm the fix
  6. •Learn - If this was a non-obvious fix, auto-invoke /learn store bug "..." to remember it

Agent Delegation

code
Task(explore, "Investigate the bug: $ARGUMENTS. Find relevant files, trace the issue.")
Task(tester, "Create a failing test that reproduces: $ARGUMENTS")
Task(implementer, "Fix the bug based on findings: [summary from explore]")
Task(reviewer, "Quick review of the fix for quality and edge cases")

Output

Return a concise summary:

  • •Root cause: What was wrong
  • •Fix applied: What changed
  • •Files modified: List of files
  • •Verification: How it was tested
  • •Learning stored: If applicable

Remember

  • •Always store non-obvious bug fixes as learnings
  • •Check if similar bugs were fixed before (recall learnings)
  • •Run tests after fixing