01
What this skill does
Use this skill to resolve hack-review reports or equivalent feedback. It verifies current ownership, accounts for findings, intentional exceptions, and coverage gaps, and reconciles stale items individually. Already-authorized fixes continue while real external-boundary guards, source feedback, and unrelated work are preserved. Follow-up review is bounded to affected changes when justified. Invocation is explicit-only: a user must invoke `$receiving-hack-review`; matching prompts do not activate it automatically.
02
When to use it
- 01Verifying that each hack-risk finding still applies to the current diff.
- 02Fixing ownership problems without mechanically deleting necessary guards.
- 03Closing or carrying forward `Not covered` ownership boundaries.
03
How it works
- 01
Read the report and requested outcome, preserving the source while enumerating findings, exceptions, and coverage gaps.
- 02
Verify current ownership and intent per item; reconcile stale claims without blocking independent confirmed work.
- 03
Create a disposition ledger: fix, disprove, narrow, confirm, or carry forward.
- 04
Apply already-authorized fixes with focused verification and respect real external-input guards and bounded exceptions.
- 05
Report every disposition and open gate item; use follow-up review only when justified, without recursive receiving cycles.
04
What you get back
- 01A disposition ledger for the entire report.
- 02Evidence-backed code changes for confirmed items.
- 03A summary of disproven, narrowed, intentional, and carried-forward items.
05
Important boundaries
- 01Do not execute the report mechanically.
- 02Preserve existing staged contents; perform Git actions only within the user's specific authorization for this task.
- 03Resolve technical risk with evidence or a narrower fix; ask only for an unresolved user decision or additional scope.
06