Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

review-pr

Sterne2

Forks0

Aktualisiert10. Juli 2026 um 01:31

Review an existing GitHub PR with full codebase context — fetches the PR and drives code-review against its merge-base. Use when the user asks to review a PR (incoming, a collaborator's, or an already-pushed one).

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

MaxWolf-01

MaxWolf-01/agents

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	review-pr
description	Review an existing GitHub PR with full codebase context — fetches the PR and drives code-review against its merge-base. Use when the user asks to review a PR (incoming, a collaborator's, or an already-pushed one).
argument-hint	<PR number or branch>

Review PR

Fetch the PR, then run the /mx:code-review skill with the PR's merge-base as fixed point and its description as spec. Arguments: $ARGUMENTS

Process

Fetch the PR: gh pr view <n> (title, description), gh pr view <n> --comments (prior discussion), gh pr view <n> --json baseRefName,headRefName.
Get the code locally: if the head branch isn't already checked out, gh pr checkout <n> — in a fresh /tmp clone when the working tree is dirty or must stay untouched.
Run the code-review skill with:
- fixed point = the PR's base branch (the three-dot diff lands on the merge-base),
- the PR title + description + any linked issues as the spec source,
- prior review discussion passed to the sub-agents, so settled points aren't relitigated.
Report: prepend **What it does**: 1–2 sentences, end to end. to the aggregated three-axis report. A clean PR gets a short review — don't invent concerns to fill space.

Mehr aus diesem Repository

gleiches Repository

dispatch

MaxWolf-01/agents

Work a feature's ticket DAG in parallel — one orchestrator fans independent frontier tickets out to parallel worker agents and integrates them on the feature branch until the feature ships. Use when a ticketed feature has independent frontier tickets, the user says "dispatch" or wants tickets worked in parallel, or when another skill routes parallel frontier work here.

2026-07-102

orient

MaxWolf-01/agents

Which mx skill or flow fits the current situation — a router over the mx workflow.

2026-07-102

tmux

MaxWolf-01/agents

Run commands in tmux whenever they run long or need eyes on them — anything expected to take more than ~30–60s (training runs, ML experiments, builds, servers), anything worth observing mid-run (progress logs, monitoring output), and anything interactive (sudo prompts, REPLs, wizards), locally or on a remote host. Always reach for this instead of a fire-and-forget Bash call in those cases — the human can attach and step in at any time.

2026-07-102

to-tickets

MaxWolf-01/agents

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published per the tracker conventions — ticket files with blocked-by edges, or native blocking links on a real tracker.

2026-07-102

permissions-review

MaxWolf-01/agents

Review and update Claude Code's auto-approved command allowlist based on Bash commands that triggered permission prompts in recent sessions.

2026-07-102

to-spec

MaxWolf-01/agents

Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

2026-07-102

name	review-pr
description	Review an existing GitHub PR with full codebase context — fetches the PR and drives code-review against its merge-base. Use when the user asks to review a PR (incoming, a collaborator's, or an already-pushed one).
argument-hint	<PR number or branch>

Review PR

Fetch the PR, then run the /mx:code-review skill with the PR's merge-base as fixed point and its description as spec. Arguments: $ARGUMENTS

Process

Fetch the PR: gh pr view <n> (title, description), gh pr view <n> --comments (prior discussion), gh pr view <n> --json baseRefName,headRefName.
Get the code locally: if the head branch isn't already checked out, gh pr checkout <n> — in a fresh /tmp clone when the working tree is dirty or must stay untouched.
Run the code-review skill with:
- fixed point = the PR's base branch (the three-dot diff lands on the merge-base),
- the PR title + description + any linked issues as the spec source,
- prior review discussion passed to the sub-agents, so settled points aren't relitigated.
Report: prepend **What it does**: 1–2 sentences, end to end. to the aggregated three-axis report. A clean PR gets a short review — don't invent concerns to fill space.