/inspect
Inspect one exact request snapshot and publish any findings autonomously.
/inspect receives the delivery context from /ready, or in standalone mode
asks for the plan, item, and exact request. It binds one complete review to one
frozen request snapshot and publishes every valid finding without manual
curation.
How /inspect closes the delivery loop
01 · AutonomousFreeze request snapshotBind the complete request, review activity, and plan to one exact head SHA.
Inspection loop
02 · AutonomousInspect and publishReview the frozen change and publish each unseen, evidence-based finding once.
Blocking findings/workPersist and execute corrective todos.New snapshot via /ready03 · OutcomeApply
agent-inspectedMark the item as inspected, then move it to review and stop. Merge and /done remain human decisions.Skill used under the hood
What /inspect does
| 1 | Snapshot | Freeze the complete open request, its review activity, authoritative plan, and head SHA. |
|---|---|---|
| 2 | Inspect | Use the reviewer profile to produce one complete SHA-bound result with persistent finding IDs. |
| 3 | Publish | Publish each unseen finding once for the unchanged SHA and observe the provider result. |
| 4 | Resolve | Return blocking findings to /work; otherwise apply agent-inspected, move the item to review, and stop without invoking /done. |
A failed review transition leaves the inspection label applied and reports an incomplete delivery with the exact remaining status update.