Review plan
Plan type review — always executed in REPORT mode: findings only, no code change, no
commit. The review contract (scope, finding fields, severities, dimensions, verdict) is
references/review.md; read it before planning.
Procedure
- Language — resolve
lang (references/language.md).
- Fix the scope — resolve the argument into an explicit
BASE..TARGET range:
- a feature slug →
base_commit from its progress.md/plan.done.md to HEAD;
- "last N commits" →
HEAD~N..HEAD; a branch → $(git merge-base main <branch>)..<branch>;
- paths only → the range that last touched them, confirmed with the human.
Record (audit on):
sh "<plugin-root>/scripts/audit-log.sh" event review "" scope <base>..<target>.
Build the package: sh "<plugin-root>/scripts/review_package.sh" <base> <target> .planning/feat/features/{slug}/review [-- <paths>]. Exit 2/3 (bad or empty range) → stop
and ask; never widen the scope silently.
- Method — follow
references/pwdevia-method.md with plan_type: review:
- Persona: senior code reviewer for the stack in
context/architecture.md.
- §3 lists the package files, the project instructions file,
context/conventions.md,
context/concerns.md and, when reviewing a feature, its plan.md.
- §4 lists ONLY
.planning/feat/features/{slug}/review.md (rendered from
templates/review-report.md) — this is what puts the executor in REPORT mode. Do not name it
report.md: some runtimes refuse subagent writes to report-like names.
- §5: every finding has id, severity,
path:line, rule citation, evidence and suggestion;
the five dimensions are covered; lint/test commands run on the target and recorded.
- After execution, when the verdict is
CHANGES_REQUESTED, offer to turn the report's fix
scope into a fix plan (feat-feature or feat-quick), citing the report in §3.
Prohibitions
- Never fix code in a review plan, and never list project files in §4.
- Never skip the security dimension.
- Never rate a cosmetic issue above LOW, or a finding without a rule citation above LOW.
- Never move HEAD in the working checkout — use a temporary worktree to inspect other states.
Language: resolve lang per references/language.md before any human-facing output. Safety: never read or expose .env* (except .env.example/.template/.sample), keys, certificates or credentials — references/safety.md. Paths references/, scripts/, templates/, schemas/ are relative to the plugin root (references/runtime.md).
1---2name: feat-review3description: >4 Use when the user wants a code review of an explicit range or set of files — correctness,5 security, performance, conventions, tests — with stable findings (CR-nnn, BLOCKER..INFO) and6 rule citations — 'revisar os últimos commits', 'code review da feature X', 'review7 base..HEAD'. Plans a REPORT-mode review (no code changes, no commit). Do NOT use to fix code8 (feat-feature / feat-quick), to write tests (feat-test) or for UI/UX design critique.9metadata:10 source: https://skillmd.com/skills/pwdev-solucoes/feat-review11 version: 3.2.112---1314# Review plan1516Plan type **review** — always executed in **REPORT** mode: findings only, no code change, no17commit. The review contract (scope, finding fields, severities, dimensions, verdict) is18`references/review.md`; read it before planning.1920## Procedure21221. **Language** — resolve `lang` (`references/language.md`).232. **Fix the scope** — resolve the argument into an explicit `BASE..TARGET` range:24 - a feature slug → `base_commit` from its `progress.md`/`plan.done.md` to `HEAD`;25 - "last N commits" → `HEAD~N..HEAD`; a branch → `$(git merge-base main <branch>)..<branch>`;26 - paths only → the range that last touched them, confirmed with the human.27 Record (audit on): `sh "<plugin-root>/scripts/audit-log.sh" event review "" scope <base>..<target>`.28 Build the package: `sh "<plugin-root>/scripts/review_package.sh" <base> <target>29 .planning/feat/features/{slug}/review [-- <paths>]`. Exit 2/3 (bad or empty range) → stop30 and ask; never widen the scope silently.313. **Method** — follow `references/pwdevia-method.md` with `plan_type: review`:32 - Persona: senior code reviewer for the stack in `context/architecture.md`.33 - §3 lists the package files, the project instructions file, `context/conventions.md`,34 `context/concerns.md` and, when reviewing a feature, its `plan.md`.35 - §4 lists ONLY `.planning/feat/features/{slug}/review.md` (rendered from36 `templates/review-report.md`) — this is what puts the executor in REPORT mode. Do not name it37 `report.md`: some runtimes refuse subagent writes to report-like names.38 - §5: every finding has id, severity, `path:line`, rule citation, evidence and suggestion;39 the five dimensions are covered; lint/test commands run on the target and recorded.404. After execution, when the verdict is `CHANGES_REQUESTED`, offer to turn the report's fix41 scope into a fix plan (`feat-feature` or `feat-quick`), citing the report in §3.4243## Prohibitions4445- Never fix code in a review plan, and never list project files in §4.46- Never skip the security dimension.47- Never rate a cosmetic issue above LOW, or a finding without a rule citation above LOW.48- Never move HEAD in the working checkout — use a temporary worktree to inspect other states.4950Language: resolve `lang` per `references/language.md` before any human-facing output. Safety: never read or expose `.env*` (except `.env.example`/`.template`/`.sample`), keys, certificates or credentials — `references/safety.md`. Paths `references/`, `scripts/`, `templates/`, `schemas/` are relative to the plugin root (`references/runtime.md`).