Stats
Actions
Tags
From arcforge
When receiving code review, verifies feedback against actual codebase usage before implementing. Handles YAGNI evaluation and provides structured pushback patterns.
How this skill is triggered — by the user, by Claude, or both
Slash command
/arcforge:arc-receiving-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Verify before implementing. Ask before assuming. Technical correctness over social comfort.
Verify before implementing. Ask before assuming. Technical correctness over social comfort.
IF any item is unclear: STOP - do not implement anything yet ASK for clarification on ALL unclear items
WHY: Partial understanding = wrong implementation
From your human partner:
If external feedback conflicts with human partner:
Pushback examples:
"I checked the current usage and this endpoint isn't called. Do we want to remove it (YAGNI) or keep it for future use?"
"This change would drop support for <legacy target>. If we still need that target, I can fix the issue without removing support."
IF reviewer suggests "implementing properly": grep codebase for actual usage IF unused: "This isn't called. Remove it (YAGNI)?"
When all feedback items are implemented and tested:
Autonomous mode (agent-driven / looping):
arc-requesting-review — loop until reviewer approvesarc-verifying to confirm all requirements and tests passarc-finishing (Step 0 discriminates on .arcforge-epic)Manual mode (human-in-loop):
npx claudepluginhub gregoryho/arcforge --plugin arcforgeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.