Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

pr-review-with-claude

Étoiles2

Forks0

Mis à jour8 juin 2026 à 09:48

A two-pass PR review with Claude that catches the boring stuff *and* asks the questions a senior engineer at Planes would actually ask.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

teamplanes

teamplanes/hangar

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

SKILL.md

readonly

name	pr-review-with-claude
description	A two-pass PR review with Claude that catches the boring stuff and asks the questions a senior engineer at Planes would actually ask.

What it does

A two-pass PR review with Claude that catches the boring stuff and asks the questions a senior engineer at Planes would actually ask.

When to use

Any PR larger than ~150 lines
Refactors or migrations where the diff lies about intent
When you're the only reviewer and want a second pair of eyes before merging

The skill

Pass 1. Mechanics. From the repo root:

gh pr diff <number> | claude -p "Review this diff. List, briefly: \
- correctness bugs you're confident in, \
- type/null/edge-case issues, \
- inconsistencies with the surrounding codebase. \
Don't list nits or style. Don't congratulate."

Pass 2. Intent. In the same Claude session:

Now zoom out. What is this PR actually trying to do? Restate it in one sentence. Then tell me:

what would a senior engineer at this codebase push back on?

what's the smallest thing this PR is missing that would make me confident it shipped safely?

if I had to delete one of these changes, which one would I delete and why?

Pass 3 (optional). Tests. If the PR doesn't touch tests:

Suggest the two highest-leverage test cases this PR should add. For each: the scenario, the expected outcome, and where the test should live in this repo.

Notes

The "delete one change" question is the killer one. It usually surfaces the scope creep nobody noticed. If Claude can't restate the PR's intent in one sentence, that's the review feedback right there: the PR doesn't know what it is.

Plus depuis ce dépôt

même dépôt

planes-deck

teamplanes/hangar

Use when building or recreating a Planes-style presentation deck: a playback, pitch, demo, strategy or client deck in the studio's house design (the "big playback deck" look people liked). Also use when someone wants an on-brand HTML slide deck with Planes fonts, colours, transitions and layouts, or asks to "make a deck like the Lewis Silkin playback" or "build a deck in the Planes style".

Use when writing, rewriting, or reviewing any copy that should sound like Planes: pitch decks, proposals, playbacks, credentials and RFP responses, website and product copy, case studies, emails, taglines, headlines, or any client-facing or internal writing that needs to be on brand. Also use when copy reads generic, corporate, hypey, or off-voice and someone wants it to "sound like us" or "sound like Planes".

Designs a collaborative workshop and builds it as a ready-to-run FigJam board, plus a facilitator run-sheet and a participant invite email. Use this skill whenever Fiona (or anyone at Planes) wants to plan, design, structure, or build a workshop, session, or facilitated meeting — and especially whenever FigJam is mentioned. Trigger on phrases like "create a workshop", "design a workshop", "build a FigJam board", "set up a workshop in FigJam", "I'm running a session with [client]", "plan a discovery workshop", "kickoff workshop", "ideation session", "retro board", "prioritisation workshop", "journey mapping session", "we need a workshop for X", "turn this into a FigJam", or any request to prepare a participatory session. Always use this skill for workshop design even if the person doesn't say "FigJam" explicitly — it produces the agenda, the board, the run-sheet, and the invite together so the whole session is ready to facilitate.

name	pr-review-with-claude
description	A two-pass PR review with Claude that catches the boring stuff and asks the questions a senior engineer at Planes would actually ask.

What it does

A two-pass PR review with Claude that catches the boring stuff and asks the questions a senior engineer at Planes would actually ask.

When to use

Any PR larger than ~150 lines
Refactors or migrations where the diff lies about intent
When you're the only reviewer and want a second pair of eyes before merging

The skill

Pass 1. Mechanics. From the repo root:

gh pr diff <number> | claude -p "Review this diff. List, briefly: \
- correctness bugs you're confident in, \
- type/null/edge-case issues, \
- inconsistencies with the surrounding codebase. \
Don't list nits or style. Don't congratulate."

Pass 2. Intent. In the same Claude session:

Now zoom out. What is this PR actually trying to do? Restate it in one sentence. Then tell me:

what would a senior engineer at this codebase push back on?

what's the smallest thing this PR is missing that would make me confident it shipped safely?

if I had to delete one of these changes, which one would I delete and why?

Pass 3 (optional). Tests. If the PR doesn't touch tests:

Suggest the two highest-leverage test cases this PR should add. For each: the scenario, the expected outcome, and where the test should live in this repo.