메뉴
Use when encountering compile errors, test failures, runtime exceptions, or unexpected behavior during implementation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | error-recovery |
| description | Use when encountering compile errors, test failures, runtime exceptions, or unexpected behavior during implementation. |
Use this skill when something goes wrong during implementation.
| Type | Examples | Priority |
|---|---|---|
| Compile / build error | Missing import, type mismatch, syntax error | Fix immediately |
| Test failure | Assertion failed, timeout, unexpected output | Fix immediately |
| Lint / static analysis | Unused variable, style violation | Fix before marking done |
| Runtime error | Panic, null pointer, unhandled exception | Fix immediately |
| Logic error | Wrong output, missing edge case | Investigate then fix |
If 3 fix attempts fail, report to the user:
Error: [exact error message]
File: [file:line]
Attempts:
1. [what you tried] → [result]
2. [what you tried] → [result]
3. [what you tried] → [result]
Hypothesis: [what you think the underlying issue is]
Suggested next step: [what a human should check]
// nolint, @SuppressWarnings, or equivalent without justification.any) to avoid a type error.Before marking error recovery as complete, verify:
Use for general product implementation work that is not primarily backend architecture, pure integration wiring, or screenshot-driven design-to-code.
Use when backend work requires contract-first thinking, schema changes, permission checks, side-effect analysis, or test planning.
Use immediately after codebase discovery to classify task scale and determine which workflow steps are required vs. optional.
Use when the user provides screenshots, mockups, or design assets and wants implementation that stays visually close to the source.
Use when the main deliverable is maintainable documentation such as repository rules, onboarding guides, runbooks, ADRs, or architecture notes.
Use when a request needs system-level planning before implementation, especially for cross-module, high-risk, or ambiguous work.