메뉴
Use when diagnosing a bug, failing test, build issue, or unexpected behavior in Cursor before proposing a fix. Focus on reproducing the issue, tracing the cause, and validating the repair.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when the user asks to review a pull request or diff with a structured Codex CLI workflow using parallel review passes and filtered actionable findings.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when the user asks to build a new feature and wants a structured Codex CLI workflow with discovery, clarifying questions, architecture comparison, implementation, and review.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
| name | systematic-debugging |
| description | Use when diagnosing a bug, failing test, build issue, or unexpected behavior in Cursor before proposing a fix. Focus on reproducing the issue, tracing the cause, and validating the repair. |
Find the root cause before making changes.
test-driven-development when possible.verification-before-completion.