القائمة
Read-only qualitative review for Task Takeover implementations before PR creation. Use after task takeover execution completes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | task-takeover-review |
| description | Read-only qualitative review for Task Takeover implementations before PR creation. Use after task takeover execution completes. |
Review the implemented changes against the task acceptance criteria and the approved plan. This is a review-only stage.
Do not edit, format, generate, stage, commit, or write files. Do not apply fixes. If the implementation needs changes, report them in feedback so the workflow can start a separate implementation container.
If you find a repo-local review skill or instruction that tells you to fix issues, use only its review checklist and validation guidance. Skip all file-editing, formatting, staging, committing, and autofix steps.
AGENTS.md, .agents/, CLAUDE.md, .claude/, README.md, CONTRIBUTING.md, Makefile targets, and any repo-local skills or agent instructions.git diff origin/main...HEAD --no-color when available, and fall back to the diff supplied in the task prompt.Evaluate these items:
The verdict format is a forge protocol constraint. Use it exactly:
verdict: adequate
or
verdict: tests_incomplete
Followed by:
feedback: <specific, actionable description of what needs to change, or "All checks passed." if adequate>
Only these two verdict values are valid. Do not use any other string.
Produce a concrete implementation plan for a standalone Task or Epic takeover ticket. Use when a Jira Task/Epic is approved for Task Takeover planning and needs target files, implementation steps, tests, and repository scope.
Decompose a Technical Specification into implementable Epics with technical plans. Use when asked to break down features, create epics, or plan implementation.
Break down Epic implementation plans into concrete, actionable Tasks. Use when decomposing Epics into implementation units.
Implement code changes according to Task specifications. Use when executing implementation Tasks.
Produce a concrete implementation plan for a bug fix from an approved RCA and selected fix approach. Use when the team has selected a fix option and needs a detailed plan before implementation.
Revise a bug fix implementation plan based on reviewer feedback. Use when the team has reviewed a plan and requested changes before approving.