From afyapowers
Use when the current afyapowers phase is review — performs 2-step code review (spec compliance + quality)
npx claudepluginhub iclinic/devex-marketplace --plugin afyapowersThis skill uses the workspace's default tool permissions.
Perform a comprehensive 2-step code review of the completed feature implementation.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
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.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Perform a comprehensive 2-step code review of the completed feature implementation.
.afyapowers/features/active to get the active feature.afyapowers/features/<feature>/state.yaml — confirm current_phase is review.afyapowers/features/<feature>/artifacts/design.md — the requirements.afyapowers/features/<feature>/artifacts/plan.md — the implementation plangit log and git diff to identify the relevant commits).afyapowers/features/<feature>/artifacts/implementation-concerns.md if it exists — these are concerns flagged by implementers during the implementation phaseDispatch a spec-reviewer subagent using skills/implementing/spec-reviewer-prompt.md:
implementation-concerns.md (or "No concerns were flagged." if the file doesn't exist)If the reviewer finds spec gaps:
Dispatch a code-quality-reviewer subagent using skills/reviewing/code-reviewer.md:
implementation-concerns.md (or "No concerns were flagged." if the file doesn't exist)If the reviewer finds issues:
Read the template from templates/review.md. Fill in:
Save to .afyapowers/features/<feature>/artifacts/review.md
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.