gregoryho/arc-receiving-review
skills/arc-receiving-review/SKILL.md
Use when receiving code review feedback, requires technical rigor not performative agreement
development
Updated Apr 5, 2026
$ install --global
skillsauthnpx skillsauth add gregoryho/arcforge arc-receiving-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:36 PM1.8s1 file scanned
SKILL.md
- name:
- arc-receiving-review
- description:
- Use when receiving code review feedback, requires technical rigor not performative agreement
arc-receiving-review
Core Principle
Verify before implementing. Ask before assuming. Technical correctness over social comfort.
The Response Pattern
- READ: Complete feedback without reacting
- UNDERSTAND: Restate requirement in own words (or ask)
- VERIFY: Check against codebase reality
- EVALUATE: Technically sound for THIS codebase?
- RESPOND: Technical acknowledgment or reasoned pushback
- IMPLEMENT: One item at a time, test each
Forbidden Responses
- ❌ "You're absolutely right!"
- ❌ "Great point!" / "Excellent feedback!"
- ❌ "Let me implement that now" (before verification)
- ❌ ANY gratitude expression ("Thanks for...")
Handling Unclear Feedback
IF any item is unclear: STOP - do not implement anything yet ASK for clarification on ALL unclear items
WHY: Partial understanding = wrong implementation
Source-Specific Handling
From your human partner:
- Trusted input, implement after understanding
- Still ask if scope is unclear
- No performative agreement
If external feedback conflicts with human partner:
- Stop and discuss with your human partner before implementing
When To Push Back
- Suggestion breaks existing functionality
- Reviewer lacks full context
- Violates YAGNI (unused feature)
- Technically incorrect for this stack
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."
YAGNI Check
IF reviewer suggests "implementing properly": grep codebase for actual usage IF unused: "This isn't called. Remove it (YAGNI)?"
After This Skill
When all feedback items are implemented and tested:
Autonomous mode (agent-driven / looping):
- Request re-review via
arc-requesting-review— loop until reviewer approves - Once approved → run
arc-verifyingto confirm all requirements and tests pass - Then use
arc-finishing(regular branch) orarc-finishing-epic(worktree with.arcforge-epic)
Manual mode (human-in-loop):
- Signal completion to user — they decide whether to re-review, verify, or finish
Integration
- Called by: arc-agent-driven, arc-requesting-review
- Related: arc-verifying (verification mindset)
Related Skills
gregoryho/arc-auditing-spec
testing
VerifiedTrustedCommunity
Use when the user explicitly runs the slash command `/arc-auditing-spec <spec-id>` to produce a read-only advisory audit of an arcforge SDD spec family (design.md, spec.xml, dag.yaml). Only triggered by direct user invocation; never auto-invoked from any pipeline skill (arc-brainstorming, arc-refining, arc-planning).
6SKILL.mdUpdated May 2, 2026
gregoryho/arc-maintaining-obsidian
development
VerifiedTrustedCommunity
Use when the user wants to create, query, audit, or initialize an Obsidian vault — wiki / knowledge base / second brain, project tracker, news pipeline, journal, or any typed-note vault. Trigger on saving notes / capturing ideas / sharing URLs to document; querying the vault ("what do I know about", "search my vault"); auditing health (missing links, orphans, drift); ingesting raw files; "init a new vault" or "register vault"; mentions of any registered vault. Also triggers on casual "save this" / "file this back". Do NOT trigger for Excalidraw diagram creation (use arc-diagramming-obsidian), general code, debugging, PR reviews, web searches.
6SKILL.mdUpdated Apr 20, 2026
gregoryho/arc-writing-skills
testing
VerifiedTrustedCommunity
Use when maintaining ArcForge itself by creating, editing, or verifying ArcForge skills before deployment
6SKILL.mdUpdated Apr 5, 2026
gregoryho/arc-verifying
testing
VerifiedTrustedCommunity
Use when you need to verify work is complete before making completion claims
6SKILL.mdUpdated Apr 5, 2026