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

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

pr-review-cycle

Étoiles2

Forks0

Mis à jour14 juin 2026 à 07:22

Interactive PR review and merge workflow. Use this skill whenever the user wants to review PRs, merge pull requests one by one, test branches, do a PR review cycle, or says things like 'review PRs', 'merge PRs', 'check open PRs', 'go through pull requests', 'test and merge', or 'PR review'. Also trigger when the user references reviewing, testing, or merging multiple PRs in sequence on any GitHub repo.

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

DotanVG

DotanVG/Orbital-Breach

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

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name

pr-review-cycle

description

PR Review Cycle

An interactive workflow for reviewing, testing, and merging open PRs one at a time. The user tests each PR locally or via Vercel preview, then approves or rejects before moving to the next.

Workflow

1. Audit

Fetch the latest state and build the review queue:

git fetch --all --prune
gh pr list --state open --json number,title,headRefName,baseRefName,additions,deletions,commits --limit 50

For each PR, also check related issues (look for "Closes #N" in PR body) and merge conflict status.

2. Plan Review Order

Sort PRs into a numbered queue:

Group by base branch - staging/dev PRs before main PRs
Within each group, smallest first by lines changed
Dependencies last - if PR B depends on PR A, review A first
Batch merges last

Present as numbered table: PR number, title, branch, base, size, related issue.

3. Interactive Review Loop

For each PR:

Load for testing:

Check out branch: gh pr checkout NUMBER
If web project, confirm Vercel preview URL or start local dev server
Brief diff summary and where to test

Wait for verdict:

Approve: gh pr merge NUMBER --merge --delete-branch, move to next
Reject/Skip: note reason, skip, circle back later
Fix needed: help fix on branch, push, re-present

After each merge:

Confirm success and branch deleted
Show remaining count
Check if later PRs now have conflicts

4. Final Batch Merge

If staging-to-main PR exists at end:

Confirm all staging PRs merged
Show full staging vs main diff
On approval, merge

5. Wrap Up

Report merged, skipped, and remaining PRs/issues.

Notes

Use --merge (not squash/rebase) unless user says otherwise
On conflicts, show files and ask how to proceed
Provide Vercel preview URLs when available
Keep responses concise - user wants to move fast

Plus depuis ce dépôt

même dépôt

threejs-atmosphere-aerial-perspective

DotanVG/Orbital-Breach

Implement physically motivated sky and aerial-perspective systems in Three.js. Use for planetary atmospheres, ground-to-space transitions, Rayleigh/Mie scattering, precomputed LUTs, depth-based transmittance and inscattering, sun/moon discs, and atmosphere-aware lighting.

2026-06-222

threejs-bloom

DotanVG/Orbital-Breach

Implement production bloom in advanced Three.js scenes. Use for HDR signal ordering, bloom-node controls, dual selective bloom with guaranteed material restoration, scene-relative emissive hierarchy, and effect-isolation diagnostics.

2026-06-222

threejs-camera-direction

DotanVG/Orbital-Breach

Direct advanced Three.js camera systems. Use for scale-aware chase rigs, thrust lag, side/orbit cameras, body-relative up vectors, quaternion handoffs, authored cinematic framing, floating origins, pointer-look controls, camera collision constraints, projection ownership, and lifecycle restoration.

2026-06-222

threejs-exposure-color-grading

DotanVG/Orbital-Breach

Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.

2026-06-222

threejs-image-pipeline

DotanVG/Orbital-Breach

Build a deliberate final-image pipeline for advanced Three.js scenes. Use for depth, normal, albedo, and history ownership; GTAO or bent normals; bloom; eye adaptation; tone mapping; 3D LUT grading; effect-local render targets; and pass diagnostics.

2026-06-222

threejs-procedural-animation

DotanVG/Orbital-Breach

Build advanced procedural animation in Three.js. Use for launch kinematics, gravity turns, staging, spin docking, target-frame decomposition, spring-follow motion, rotating-frame alignment, peeling debris, analytic transform timelines, frame-rate-independent response, and quaternion control.

2026-06-222

name

pr-review-cycle

description

PR Review Cycle

An interactive workflow for reviewing, testing, and merging open PRs one at a time. The user tests each PR locally or via Vercel preview, then approves or rejects before moving to the next.

Workflow

1. Audit

Fetch the latest state and build the review queue:

git fetch --all --prune
gh pr list --state open --json number,title,headRefName,baseRefName,additions,deletions,commits --limit 50

For each PR, also check related issues (look for "Closes #N" in PR body) and merge conflict status.

2. Plan Review Order

Sort PRs into a numbered queue:

Group by base branch - staging/dev PRs before main PRs
Within each group, smallest first by lines changed
Dependencies last - if PR B depends on PR A, review A first
Batch merges last

Present as numbered table: PR number, title, branch, base, size, related issue.

3. Interactive Review Loop

For each PR:

Load for testing:

Check out branch: gh pr checkout NUMBER
If web project, confirm Vercel preview URL or start local dev server
Brief diff summary and where to test

Wait for verdict:

Approve: gh pr merge NUMBER --merge --delete-branch, move to next
Reject/Skip: note reason, skip, circle back later
Fix needed: help fix on branch, push, re-present

After each merge:

Confirm success and branch deleted
Show remaining count
Check if later PRs now have conflicts

4. Final Batch Merge

If staging-to-main PR exists at end:

Confirm all staging PRs merged
Show full staging vs main diff
On approval, merge

5. Wrap Up

Report merged, skipped, and remaining PRs/issues.

Notes

Use --merge (not squash/rebase) unless user says otherwise
On conflicts, show files and ask how to proceed
Provide Vercel preview URLs when available
Keep responses concise - user wants to move fast