Run any Skill in Manus with one click

aeview-pr

Stars2

Forks0

UpdatedJune 16, 2026 at 02:50

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

MarlzRana

MarlzRana/aeview

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	aeview-pr
description	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.
argument-hint	[<pr-number>] [--checkout new\|current\|none] [--reviewers a,b] [aeview run flags]
disable-model-invocation	true

aeview-pr

Review a pull request with the aeview panel. Review-only — do not change code unless the user explicitly asks for a fix.

Raw arguments: $ARGUMENTS

1. Resolve the PR + flags

PR number: the first bare number in the arguments. If none, the current branch's PR: gh pr view --json number -q .number.
--checkout new|current|none: how to make the PR's files available to reviewers (step 2). If omitted, ask.
Everything else (--reviewers a,b, --include-dirty, …) forwards to aeview run.

2. Check out the PR

aeview run --scope pr:<n> gets the diff via gh, but reviewers read the working tree — for changed files that's the wrong version unless the PR is checked out. Read the PR-checkout reference and follow it: honor --checkout, else offer new-worktree (recommended) / current / none.

3. Run the review (prefer the background)

From the chosen location (the PR worktree, the current repo, or wherever you are for no-checkout). Always pass --json (these skills are agent-driven; the JSON gate is the reliable contract). A full panel takes a few minutes, so run it as a background task rather than blocking:

aeview run --scope pr:<n> --json [--reviewers …] [flags]

It prints its run id on stderr; let it finish (aeview status <run-id> --wait), then read the JSON gate and present the review faithfully — verdict + each finding (severity, file:line, title, recommendation). Do not editorialize or propose fixes. The exit code is the verdict: 0 approve · 1 needs-attention · 2 error; full report via aeview result <run-id>.

4. Stop

After presenting the review, STOP. Do not fix anything on your own initiative — apply fixes only if the user explicitly asks, or point them to the aeview-loop skill.

More from this repository

same repository

aeview-loop

MarlzRana/aeview

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.

2026-07-052

aeview-loop-with-confirmation

MarlzRana/aeview

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.

2026-07-052

aeview-install

MarlzRana/aeview

Install the aeview CLI and its reviewer-panel skills on this machine, then verify the setup.

2026-06-192

aeview-commits

MarlzRana/aeview

Review one or more specific commits with the aeview reviewer panel. Presents the review and stops; does not change code unless you explicitly ask.

2026-06-162

aeview-effective-pr

MarlzRana/aeview

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.

2026-06-162

aeview

MarlzRana/aeview

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.

2026-06-162

name	aeview-pr
description	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.
argument-hint	[<pr-number>] [--checkout new\|current\|none] [--reviewers a,b] [aeview run flags]
disable-model-invocation	true

aeview-pr

Review a pull request with the aeview panel. Review-only — do not change code unless the user explicitly asks for a fix.

Raw arguments: $ARGUMENTS

1. Resolve the PR + flags

PR number: the first bare number in the arguments. If none, the current branch's PR: gh pr view --json number -q .number.
--checkout new|current|none: how to make the PR's files available to reviewers (step 2). If omitted, ask.
Everything else (--reviewers a,b, --include-dirty, …) forwards to aeview run.

2. Check out the PR

3. Run the review (prefer the background)

aeview run --scope pr:<n> --json [--reviewers …] [flags]

4. Stop

After presenting the review, STOP. Do not fix anything on your own initiative — apply fixes only if the user explicitly asks, or point them to the aeview-loop skill.