메뉴
Run the project's verification commands before claiming work complete. Use ALWAYS when finishing a task, claiming work done, committing, or creating a PR. Blocks completion until all checks pass.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create atomic GitHub issues with clear acceptance criteria. Use when breaking down work into single-iteration tasks that can be picked up and completed independently.
Create well-structured GitHub milestones. Use when planning new phases of work that group related issues together.
Background knowledge about npm native binary corruption in Docker sandboxes
Laravel invokable controller patterns with Inertia. Use when creating endpoints, adding pages, building CRUD, or when user asks to "create an endpoint", "add a controller", "build a page", "add a store action", "create show page".
Inertia.js page component patterns with TypeScript. Use when creating pages or when user asks to "create a page", "build a component".
Use when taking screenshots, PDFs, or video recordings with agent-browser in a Laravel project. Applies to any visual capture command including screenshot, pdf, and record.
| name | feedback-loops |
| description | Run the project's verification commands before claiming work complete. Use ALWAYS when finishing a task, claiming work done, committing, or creating a PR. Blocks completion until all checks pass. |
This project has specific verification commands that MUST pass before work is considered complete. These are the project's feedback loops — automated checks that catch regressions, style violations, type errors, and broken tests.
Do not claim work is done, commit code, or create a PR unless you have run the project's feedback loops and every command passed.
If any command fails, the task is not complete. Fix the failures first, re-run the full checklist, and only then claim completion.
git commit or create a commit via any toolgh pr create or open a PRIn all of these moments: stop, run the checklist below, report pass/fail for each, fix any failures, then continue.
{{ $feedback_loops_checklist }}
When you report on your work (in a PR body, completion message, or task update), include the feedback loop status. Example:
Feedback loops:
✓ composer test
✓ composer analyse
✓ composer format --test
If a command is intentionally skipped (e.g., no changes to frontend → skipping npm run types), note that explicitly.