fix

Fix

Use this skill when the user explicitly asks to fix a problem, locate a bug, or enter a debug process.

Do not use for:

• Ordinary feature implementation
• Language or framework style conventions
• Formal code review
• Environment-level risk assessment

Mode

Before entering fix, if a mainline task in the project is already in 进行中, and this fix is only a temporary insertion, first use cc-task-state or directly add an "interruption record" in the mainline task file, stating where you are, why you switched out, the recovery entry point, and the next step, then enter the fix process.

Fix Mode

Suitable for scenarios where the problem boundary is relatively clear and it can be fixed directly.

1. Confirm the expected behavior and the current symptoms.
2. Read the relevant code paths.
3. Make the minimal effective fix.
4. Perform targeted verification on the original problem path.
5. Explain residual risks.

Debug Mode

Suitable for scenarios where the symptoms are clear but the root cause is unclear.

1. Reproduce or describe the symptoms.
2. Propose specific hypotheses.
3. Verify hypotheses with low-cost checks.
4. Make the minimal fix based on evidence.
5. Regression-test the original problem path.

Supplementary checks

• When encountering frontend-backend integration, list pages, pagination, filter items, or detail page anomalies, additionally use cc-api-contract-safety
• If the fix will interrupt the current mainline task, prioritize recording a checkpoint; only create a separate task for an inserted fix if its scope is independent and it may span multiple rounds
• First verify the actual API response, the unified success response format, and the pagination structure, then decide whether to fix the backend root cause or keep a temporary frontend compatibility layer
• If a compatibility branch is kept, the exit condition must be stated, and dual-format compatibility must not be solidified long-term

Output requirements

• Clearly distinguish symptoms, hypotheses, fixes, and verification.
• If this fix interrupted a mainline task, clearly state whether a checkpoint has been added, and how the mainline is to be resumed.
• Without evidence, do not claim that the root cause has been found.
• Do not expand the problem scope just because of the debugging process.

Expand as needed

• Direct fix:references/fix-mode.md
• Structured investigation:references/debug-mode.md
• Post-fix verification:references/verification-after-fix.md