Skill

afyapowers:reviewing

Use when the current afyapowers phase is review — performs 2-step code review (spec compliance + quality)

Install

npx claudepluginhub iclinic/devex-marketplace --plugin afyapowers

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Perform a comprehensive 2-step code review of the completed feature implementation.

Supporting Assets

code-reviewer.md

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars3

Parent Repo Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Review Phase

Perform a comprehensive 2-step code review of the completed feature implementation.

Phase Gate

Read .afyapowers/features/active to get the active feature
Read .afyapowers/features/<feature>/state.yaml — confirm current_phase is review
If not in review phase, tell the user the current phase and stop

Process

Step 1: Gather Context

Read .afyapowers/features/<feature>/artifacts/design.md — the requirements
Read .afyapowers/features/<feature>/artifacts/plan.md — the implementation plan
Get the git diff for the feature's changes (use git log and git diff to identify the relevant commits)
Read .afyapowers/features/<feature>/artifacts/implementation-concerns.md if it exists — these are concerns flagged by implementers during the implementation phase

Step 2: Spec Compliance Review

Dispatch a spec-reviewer subagent using skills/implementing/spec-reviewer-prompt.md:

Provide the design spec content as "what was requested"
Provide a summary of implemented changes as "what was built"
Provide the relevant code diff
Include a "Priority Areas" section with the contents of implementation-concerns.md (or "No concerns were flagged." if the file doesn't exist)

If the reviewer finds spec gaps:

Report the findings to the user
The user fixes issues (code changes happen during review phase)
Re-dispatch the spec reviewer
Repeat until spec-compliant (max 5 iterations)

Step 3: Code Quality Review

Dispatch a code-quality-reviewer subagent using skills/reviewing/code-reviewer.md:

Provide: what was implemented, plan reference, base/head SHAs, description
Include a "Priority Areas" section with the contents of implementation-concerns.md (or "No concerns were flagged." if the file doesn't exist)

If the reviewer finds issues:

Categorize by severity (Critical, Important, Minor)
Critical and Important: must be fixed before proceeding
Minor: note for later, do not block
Fix issues and re-dispatch (max 5 iterations)

Step 4: Produce Review Artifact

Read the template from templates/review.md. Fill in:

Spec compliance findings and resolutions
Code quality findings and resolutions
Final verdict: "Approved" (only if both reviews pass)

Save to .afyapowers/features/<feature>/artifacts/review.md

Step 5: Complete

Update state.yaml to add review.md to the review phase's artifacts list. Append artifact_created event to history.yaml.

Tell the user: "Review phase complete. Run /afyapowers:next to proceed to complete."

Important: The verdict MUST be "Approved" for /afyapowers:next to accept the transition. If issues remain, keep the verdict as "Changes Requested" and work with the user to resolve them.