← ClaudeAtlas

review-setuplisted

Install the Wingman review feedback loop into the current project — git hook, .reviews/ directory, and learned patterns rule file
ashbrener/wingman · ★ 0 · Code & Development · score 60
Install: claude install-skill ashbrener/wingman
# Wingman: Setup Install the Wingman review feedback loop into the current project. ## Prerequisites Before running setup, verify: 1. The project is a git repository. 2. A reviewer CLI is available. Wingman defaults to `codex` but supports any of `codex | gemini | claude` via the `WINGMAN_REVIEWER` environment variable or a `.wingman-reviewer` repo file. The reviewer should be a **different model than the one writing the code** — that cross-model second opinion is the value. Detect which reviewer CLIs are present (`command -v codex`, `command -v gemini`, `command -v claude`) and report them. If the user's chosen reviewer is missing, print its install hint and continue — setup must NOT block on a missing reviewer (the hook degrades gracefully, writing a `reviewer_missing` review file rather than failing the push): - Codex CLI: `npm install -g @openai/codex` - Gemini CLI / Claude CLI: install per their official instructions. Note: choosing `claude` while Claude wrote the code still works, but it isn't a true cross-model opinion — prefer `codex` or `gemini` when Claude is the author. ## What to install ### 1. Pre-push git hook Detect the project's git hooks directory: - Check `git config core.hooksPath` first - Look for `.git-hooks/`, `.githooks/`, or `.husky/` directories - Fall back to `.git/hooks/` If a `pre-push` hook already exists, append the Wingman section wrapped in clearly marked comments. Do not overwrite existing hook content. The canonical hook bl