← ClaudeAtlas

review-looplisted

Run cross-model review, categorize findings, fix issues, and encode learned patterns into project rules
ashbrener/wingman · ★ 0 · Code & Development · score 60
Install: claude install-skill ashbrener/wingman
# Wingman: Review Loop Run the full review feedback loop: review code with the configured reviewer (`WINGMAN_REVIEWER`, default `codex`), present findings for user decision, fix issues, and encode learned patterns so they don't recur. ## Protocol: auto-surface after push Whenever the agent runs `git push` in a repo that has Wingman installed (detectable by the presence of the `# --- Wingman: Codex review` marker in the repo's `pre-push` hook), the review runs in the background and finishes ~60-120 seconds later. The agent MUST: 1. Return control to the user immediately after `git push` completes (the hook is non-blocking — don't wait for the review). 2. Tell the user: *"Pushed. Wingman review running in the background; I'll surface the findings table here when it's ready."* 3. Schedule a follow-up check (e.g. `ScheduleWakeup(delaySeconds: 120)`) that re-enters this skill. 4. On wake-up, scan `.reviews/*.json` for the latest file whose `status` is `needs_categorization`; if present, proceed to Step 1 below and render the findings table inline in chat, unprompted. This makes the review an ambient part of the push flow, not a manual step the developer has to remember. ## Hook version check (drift detection) <!-- CURRENT_HOOK_VERSION: keep in sync with the wingman-hook-version stamp in assets/pre-push.sample --> The current Wingman hook version is **4**. Before gathering findings, read the installed `pre-push` hook (the file containing the `# --- Wingman: C