القائمة
Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create or revise Markdown `description` frontmatter so `docgarden match` routes agents to the right repository documents. Use when adding a new routed Markdown document, updating existing frontmatter, fixing noisy or missing match results, tuning skills or docs discovery, or making descriptions more query-aligned without loading document bodies.
Guide for writing ast-grep rules to perform structural code search, analysis, and bulk rewrites/refactors. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, perform complex code queries that go beyond simple text search, or carry out structural refactors and code transformations across many files. This skill should be used when users ask to search for code patterns, find specific language constructs, locate code with particular structural characteristics, or rewrite/refactor/migrate code structurally (e.g., renaming an API across all callers, replacing a deprecated pattern, migrating call signatures) instead of reaching for sed, custom Python scripts, or one-off regex replacements.
Implement from an active plan or ExecPlan while keeping it up to date. Use when an agent needs to implement the active plan, continue plan-driven work, resume the current plan, or carry out an existing ExecPlan.
Create, update, revise, reopen, or rescope a plan or ExecPlan using `PLANS.md`. Use when an agent needs to create a plan, plan a change, update the plan with new requirements, or rewrite an active ExecPlan.
| name | evaluator-execplan |
| description | Review the current branch, PR, or worktree against the plan or ExecPlan and record findings. Use when an agent needs a code review with findings for changes associated with an active plan. |
Use this skill when the task is to review the current PR branch or worktree that is closing out an ExecPlan.
MUST READ before reviewing:
docs/PLANS.mddocs/CODESTYLE.mddocs/TESTING.mdReview against all three authorities: the ExecPlan, CODESTYLE.md, and TESTING.md. The ExecPlan defines task intent, but it is not the only acceptance criteria. If the plan conflicts with, narrows away, or omits a requirement from the code or testing docs, record that as a finding instead of accepting the plan as authoritative.
A design element that appears in the ExecPlan spec is not pre-approved against CODESTYLE.md. Apply the same scrutiny to plan-specified designs as to emergent ones.
Apply each rule at the granularity it requires. For example, if TESTING.md says individual tests must move unless they call private functions, inspect individual tests, not just whether a module contains any private-helper test.
Role-specific review responsibilities stop here; docs/PLANS.md remains the source of truth for ExecPlan structure and maintenance rules.
As evaluator, you own:
CODESTYLE.md violations, TESTING.md violations, and unnecessary complexityDefinition of Done section once the review is clean and all findings are addressedYou do not own:
Use the evaluator when the task is to perform an independent review of the current branch or worktree against the plan.
Act like a reviewer, not a closeout assistant. Record findings in the ExecPlan without softening the review to fit what was built.