After you and the user have planned and implemented a change, loop with the aeview reviewer panel until it converges — running the project's gates, reviewing with the panel, and fixing the findings each cycle. Use when a change is already written and the user wants it reviewed and fixed until it passes the gates and the panel finds no new issues — "review until clean" or "loop until the panel is happy". It fixes what the panel finds; it does not build the change from scratch. For a one-shot review with no fixes, use the aeview skill instead.
Like aeview-loop — run after you and the user have planned and implemented a change — but it pauses every cycle to confirm each reviewer finding with the user before acting. For each finding it presents the issue, tailored resolution options (always including Ignore) and its recommendation via AskUserQuestion, then applies the chosen option. Use when you want to approve every fix the loop makes; for the autonomous version use aeview-loop.
Install the aeview CLI and its reviewer-panel skills on this machine, then verify the setup.
Review one or more specific commits with the aeview reviewer panel. Presents the review and stops; does not change code unless you explicitly ask.
Review the branch's commits plus uncommitted work (the effective PR) with the aeview reviewer panel. Presents the review and stops; does not change code unless you explicitly ask.
Review a GitHub pull request with the aeview reviewer panel. Reviews the PR's diff and (by default) checks the PR out so reviewers read its real files. Presents the review and stops; does not change code unless you explicitly ask.
Review code changes with the aeview multi-harness reviewer panel. Use when the user asks to review a diff, branch, pull request, commits, or staged/working changes, wants a code review, or wants changes checked before merge or commit. You pick the scope from the request and may override reviewers and settings. Presents the review and stops; does not change code unless the user explicitly asks. For an implement-and-review loop, use the aeview-loop skill instead.
Publish a new version of aeview to PyPI through its tag-driven Trusted-Publishing GitHub Actions workflow. Use when you're cutting an aeview release — it runs preflight checks, bumps the version, pushes, tags, hands you the PyPI approval gate, then verifies the publish.