一键在 Manus 中运行任何 Skill

mega-pr

星标5

分支1

更新时间2026年5月19日 13:56

Fan-out PR review that runs BOTH `/devkit:tri-review` AND `/pr-review-toolkit:review-pr` in parallel for maximum coverage, then presents unified results — this skill does not compete with its sub-skills, it delegates to both simultaneously. Use when the user asks for "mega PR review", "mega-pr", "mega review", "full PR review with everything", "both review tools", "maximum coverage review", or explicitly wants every available reviewer looking at a change at once (Claude + Codex + Gemini model diversity PLUS specialized aspect reviewers like silent-failure-hunter, type-design-analyzer, test-analyzer, code-reviewer). Worth the extra cost when: the PR is high-stakes and the user wants every angle covered, or before merging a critical or hard-to-revert change. Do NOT use when the user only wants one review system (use tri-review or pr-review-toolkit:review-pr directly). Do NOT use for routine code review where a single reviewer suffices. This is deliberate overkill for when you want absolutely everything.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

5uck1ess

5uck1ess/devkit

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Mega PR Review

Run /devkit:tri-review and /pr-review-toolkit:review-pr simultaneously for maximum review coverage when those skills/plugins are available. Under non-Claude hosts, run devkit's tri-review MCP workflow and any available external review command; if pr-review-toolkit is not installed in the host, report that part as unavailable instead of fabricating results.

Step 1: Launch Both Reviews

[PARALLEL] — invoke both in a single message using the Skill tool:

Skill: devkit:tri-review — dispatches available model-diverse reviewers
Skill: pr-review-toolkit:review-pr — dispatches specialized aspect reviewers when the Claude plugin is installed (silent-failure-hunter, type-design-analyzer, test-analyzer, code-reviewer, etc.)

Pass any user-provided arguments (custom prompt, specific files) to both skills unchanged.

Step 2: Present Combined Results

After both complete, present a unified report:

## Mega PR Review: <branch_name>

### tri-review Results
<consensus + unique findings>

### pr-review-toolkit Results
<categorized by severity>

### Summary
- Total agents participated: <count>
- Critical issues: <count>
- Warnings: <count>
- Suggestions: <count>

Rules

Always run both in parallel — never sequential
If one skill fails, still present the other's results
Do not deduplicate — let the user see both perspectives

同仓库更多 Skills

同仓库

adr

5uck1ess/devkit

Generate Architecture Decision Records — use when asked to document a decision, create an ADR, record why we chose X, or capture architectural rationale.

2026-05-195

doc-gen

5uck1ess/devkit

Generate documentation for code — use when asked to document a module, generate API docs, create a README for code, or write reference documentation. Triggers the deterministic doc-gen workflow (analyze → generate via documenter agent → write).

2026-05-195

health

5uck1ess/devkit

Check devkit health — which external CLIs (codex, gemini, gh, rtk, sg, gcli) are installed, which agents are available, which skills are ready to use. Use when asked about devkit health, devkit status, "is devkit working?", "what's installed?", "what devkit capabilities do I have?", diagnosing devkit setup issues, or running /devkit:health. Read-only diagnostic, safe to auto-invoke.

2026-05-195

onboard

5uck1ess/devkit

Generate a codebase onboarding guide — use when asked to explain this codebase, help understand the architecture, give a tour of the repo, or onboard a new contributor. Triggers the deterministic onboard workflow (analyze structure → architect via researcher agent → write guide).

2026-05-195

pr-ready

5uck1ess/devkit

Full end-to-end PR pipeline — validate → necessity-check → lint (loop) → test (loop) → security scan → doc-check → changelog → create-pr → monitor reviews (loop). Takes a branch from "code done" to "merged" with every gate enforced. Use when the user asks to "submit a PR", "open a pull request", "ship this", "make this PR-ready", "finalize this branch", or wants the full pipeline run end-to-end with CI monitoring and reviewer-comment handling automated. Worth the ceremony when: lint and test gates must pass before the PR opens, docs need syncing alongside code (README, ROADMAP, SKILL.md, workflows), security scan is required, or the user wants reviewer comments automatically classified and responded to. Do NOT use for a quick commit+push+PR without gates — use `/commit-commands:commit-push-pr` for that lighter path. Do NOT use when already mid-PR and just handling existing review comments in isolation. Do NOT use on the main branch or with uncommitted changes — the validate step will block you. This is devkit

2026-05-195

setup-rules

5uck1ess/devkit

Install devkit coding rules to ~/.claude/rules/ for Claude Code language-specific auto-activation. Use when the user explicitly asks to set up devkit rules, install language rules, or run /devkit:setup-rules. One-shot installer with side effects (writes to ~/.claude/rules/) — user-only invocation, never auto-triggered. Under non-Claude hosts, use AGENTS.md and resources/rules/ as reference instead of installing Claude rules.

2026-05-195

name

mega-pr

description

Mega PR Review

Step 1: Launch Both Reviews

[PARALLEL] — invoke both in a single message using the Skill tool:

Skill: devkit:tri-review — dispatches available model-diverse reviewers
Skill: pr-review-toolkit:review-pr — dispatches specialized aspect reviewers when the Claude plugin is installed (silent-failure-hunter, type-design-analyzer, test-analyzer, code-reviewer, etc.)

Pass any user-provided arguments (custom prompt, specific files) to both skills unchanged.

Step 2: Present Combined Results

After both complete, present a unified report:

## Mega PR Review: <branch_name>

### tri-review Results
<consensus + unique findings>

### pr-review-toolkit Results
<categorized by severity>

### Summary
- Total agents participated: <count>
- Critical issues: <count>
- Warnings: <count>
- Suggestions: <count>

Rules

Always run both in parallel — never sequential
If one skill fails, still present the other's results
Do not deduplicate — let the user see both perspectives