Dispatched after a task lands at in_review to produce a structured CTO-grade verdict on the work and its PR. Two invocation paths: composer Phase 4 (orchestrator dispatches after the implementer's in_review write, surfaces the verdict to HOTL, stops), and direct mode from the piyaz skill on requests ("review VF-N", "review this PR", "review <PR URL>"). Reads piyaz_get lens='review' for the implementationPlan rendered alongside executionRecord, AC evaluation against executionRecord excerpts, downstream impact, and the PR handle from task.links filtered to kind='pull_request'; the PR diff is the source of truth for what changed, and tasks that ship deliverables instead of a PR are reviewed through their linked artifacts. Returns one of approve, request-changes, or block with file-cited reasoning across the security, performance, reliability, observability, and codebase standards lenses. Never auto-flips status; HOTL owns the in_review to done transition. Do not use for refinement, draft / planned review, style nits, or speculative scaling concerns outside the task's scope.
How to install review?
frkak/piyaz/review
$npx -y skills add frkak/piyaz --skill reviewInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/frkak/piyaz" --skill "frkak/piyaz/review"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/frkak/piyaz" that are relevant to the current task. Run `npx skills add "https://github.com/frkak/piyaz"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
