메뉴
Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | quick-fix |
| description | Apply a minimal, targeted fix to a specific bug or issue. Focused on speed and precision - locate the problem, make the smallest correct change, and verify. Not a planning workflow; use for small fixes, patches, and hotfixes. |
Fix a specific bug or issue with the smallest correct change. This skill prioritizes speed and precision over comprehensive refactoring.
This skill is explicitly not a planning workflow. If the fix requires:
Then use the technical-planning or refactor skill instead.
Get a clear description of the problem:
Questions to ask (if not already clear):
# Check for recent errors
git log --oneline -5 2>/dev/null
# Check test failures if applicable
npm test 2>&1 | tail -20 || echo "No test command"
Find the relevant file(s) quickly:
# Search for error-related code
grep -rn "errorKeyword" src/ --include="*.ts" --include="*.js" | head -15
# Find the function or component
grep -rn "functionName" src/ --include="*.ts" --include="*.js" | head -10
Read the file and understand the immediate context around the bug.
Make the smallest correct change:
Fix principles:
Common fix patterns:
| Bug Type | Fix Pattern |
|---|---|
| Null/undefined | Add null check or optional chaining |
| Type mismatch | Fix type or add type guard |
| Off-by-one | Correct boundary condition |
| Missing await | Add await keyword |
| Wrong condition | Fix boolean logic |
| Missing import | Add the import statement |
| Stale state | Fix dependency array or use functional update |
# Run relevant tests
npm test -- --testPathPattern="[related-test]" 2>&1 | tail -20
# Check types
npm run typecheck 2>&1 | tail -15 || tsc --noEmit 2>&1 | tail -15
# Run lint
npm run lint 2>&1 | tail -15
If the project has no tests for the affected code, verify manually and note that tests should be added separately.
## Quick Fix: [Brief Description]
### Problem
[What was wrong - one or two sentences]
### Root Cause
[Why it was wrong - one sentence]
### Fix Applied
- `path/to/file.ts:line` - [What was changed]
### Verification
- [x] Fix compiles without errors
- [x] Relevant tests pass
- [ ] No tests exist for this code (consider using test-generation skill)
### Commit Suggestion
fix(scope): [brief description of what was fixed]
Perform thorough code review and audit of implemented features. Compares implementation against the technical plan, checks for AI-specific risks, and provides actionable feedback. Activate for: review, audit, code quality assessment, security review.
Initialize Conductor workflow in a project. Bundles all necessary templates for product context, tech stack, workflow, and tracks. v1.0: Hooks handle phase enforcement - setup focuses on file creation.
Persistence mode instructions for autonomous task completion. Activated when the user includes "ralph", "persistent", or "don't give up" in their prompt. Provides structured guidance for working through tasks systematically.
Structured research methodology for finding documentation, investigating APIs, and synthesizing technical information. Guides systematic research with source verification and organized output. Activate for: research, documentation lookup, investigate, explore concepts.
Plan and design a detailed, phased technical implementation from a PRD. Creates actionable task lists with guardrails for resource efficiency, error handling, and type safety. Activate for: plan, design, technical planning, task breakdown.
Generate documentation for implemented features. The actual code is always the source of truth - document what was built, not what was planned. Creates code comments, README updates, and developer guides as appropriate.