ワンクリックでManusで任意のスキルを実行

review

スター3

フォーク0

更新日2026年3月24日 10:57

Trigger @claude PR review on a Pull Request via GitHub Actions. Use this skill whenever the user says "/review", "review the PR", "code review", "trigger review", or any request to get an automated code review on a PR. Also triggers on "claude review", "run review", or "check the PR". Posts a comment mentioning @claude which triggers the GitHub Action.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

skaisser

skaisser/blueprint

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Review: Trigger PR Code Review

Language

Read blueprint/.config.yml → language. If auto, detect from the user's messages. All generated content MUST be in the detected language. Skill instructions stay in English — only output changes.

Trigger mention-based PR review on a Pull Request.

CRITICAL GUARDRAILS:

Do NOT perform the review yourself — this skill only posts a comment to trigger the CI-based review
Do NOT modify any code files, project files, or configuration
Do NOT merge, approve, or close the PR
Do NOT run tests or make any changes to the codebase

/plan → /plan-review → /plan-approved → /plan-check → /pr → /review → /address-pr → /finish

Step 1: Get PR Number and Trigger Review

If $ARGUMENTS provided, use it as PR number
Otherwise: gh pr view --json number -q .number

If no PR found, STOP: "No open PR found. Create one with /pr first."

Then trigger the review:

gh pr comment <PR_NUMBER> --body "@claude review this PR and check if we are able to merge. Analyze the code changes for any issues, security concerns, or improvements needed."

If the comment fails (non-zero exit), STOP and report the error.

Step 2: Verify Action Triggered

Check that the GitHub Action workflow was triggered:

gh run list --workflow=claude-pr-reviewer.yml --limit=1 --json status,createdAt,event -q '.[0]'

Report the run status. If no run found, note that the action may take a moment to start or may not be configured.

Step 3: Confirm and Ask

Confirm review was triggered and provide the PR link. Review usually appears within 2-5 minutes.

STOP. You MUST use AskUserQuestion tool here.

Question: "Review triggered on PR #N. Ready to address feedback?"
Option 1: "Address review now" — Run /address-pr
Option 2: "I'll check the review first"

Use $ARGUMENTS as PR number if provided.

このリポジトリの他の Skills

同じリポジトリ

flow-auto

skaisser/blueprint

Fully autonomous SDLC pipeline — zero user intervention. Opus 4.6 runs the entire workflow from plan through PR, handles review feedback loops, and stops only when the PR is ready for human merge. Use this skill whenever the user says "/flow-auto", "auto flow", "autonomous flow", "just do everything", "full auto", "hands off", "run it all", or any request to run the complete pipeline without checkpoints or user decisions. Also triggers on "no intervention", "auto pipeline", "unattended flow", "fire and forget flow", "do everything and leave me a PR", or "I'm going to sleep just build it". This is the zero-touch version of /flow — same pipeline, no pauses. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.

2026-03-273

flow-auto-wt

skaisser/blueprint

Fully autonomous SDLC pipeline in an isolated git worktree — zero user intervention, zero git conflicts with other terminals. Creates a lightweight worktree (no Herd URL, no VS Code, no SSL), runs the full flow-auto pipeline inside it, and stops when the PR is ready for merge. Use this skill whenever the user says "/flow-auto-wt", "auto flow worktree", "parallel flow-auto", "flow-auto in worktree", or any request to run the autonomous pipeline in an isolated worktree. Also triggers on "isolated flow-auto", "worktree auto", "parallel auto", "run flow-auto in isolation", "don't touch my branch", "run in parallel", "parallel pipeline", or when running multiple flow-auto instances on the same repo. IMPORTANT: never use AskUserQuestion in this skill — all decisions are made autonomously.

2026-03-273

plan

skaisser/blueprint

Create structured implementation plans with git branches and memory search. Use this skill whenever the user wants to plan a feature, fix, refactor, or any development task. Triggers on: "/plan", "plan this", "create a plan for", "let's plan", "I need to plan", "break this into phases", "how should we approach", "let's think about how to build", or any request that involves planning, phasing, or strategizing before coding. For worktree-based plans (isolated directory), use /plan-wt instead. ALWAYS use this skill before starting implementation — planning first, coding second.

2026-03-273

start

skaisser/blueprint

Initialize a new project with GitHub Actions, git hooks, blueprint workspace, CLAUDE.md, and branches. Use this skill whenever the user says "/start", "initialize project", "setup project", "start new project", or any request to set up the standard development workflow in a repo. Also triggers on "project init", "bootstrap project", "setup hooks", or "initialize repo". Sets up everything: claude-pr-reviewer.yml + tests.yml actions, commit hooks, blueprint/ workspace, CLAUDE.md, configurable staging branch. Updates are handled by `blueprint update` — no separate sync skills needed.

2026-03-273

backlog

skaisser/blueprint

Capture, manage, and promote pre-planning ideas before they become full plans. Use this skill whenever the user says "/backlog", "add to backlog", "backlog idea", "capture this idea", "save this for later", "I had an idea", or any request to manage the idea backlog. Also triggers on "list ideas", "promote idea", "backlog list", "drop idea", "mark done", "what's in the backlog", "show me the ideas", "pending ideas", or any request to add/view/promote/done/drop items in blueprint/backlog/. The backlog is the pre-planning stage — ideas live here until promoted to /plan. Even if the user doesn't explicitly say "backlog", trigger when they describe wanting to capture a feature idea, task, or improvement for later without implementing it now. This skill is the gateway to the SDLC — nothing gets planned or built without first passing through the backlog.

2026-03-263

bp-status

skaisser/blueprint

Show quick repo status — branch, base, plan, PR info in one shot. Triggers on "/bp-status", "/status", "show status", "repo status", "what branch am I on", "current status", "where am I", "project status", "what's the current state", "which branch", "is there a PR open", "what plan am I on". Uses blueprint CLI with git fallback.

2026-03-243

name	review
description	Trigger @claude PR review on a Pull Request via GitHub Actions. Use this skill whenever the user says "/review", "review the PR", "code review", "trigger review", or any request to get an automated code review on a PR. Also triggers on "claude review", "run review", or "check the PR". Posts a comment mentioning @claude which triggers the GitHub Action.

Review: Trigger PR Code Review

Language

Trigger mention-based PR review on a Pull Request.

CRITICAL GUARDRAILS:

Do NOT perform the review yourself — this skill only posts a comment to trigger the CI-based review
Do NOT modify any code files, project files, or configuration
Do NOT merge, approve, or close the PR
Do NOT run tests or make any changes to the codebase

/plan → /plan-review → /plan-approved → /plan-check → /pr → /review → /address-pr → /finish

Step 1: Get PR Number and Trigger Review

If $ARGUMENTS provided, use it as PR number
Otherwise: gh pr view --json number -q .number

If no PR found, STOP: "No open PR found. Create one with /pr first."

Then trigger the review:

gh pr comment <PR_NUMBER> --body "@claude review this PR and check if we are able to merge. Analyze the code changes for any issues, security concerns, or improvements needed."

If the comment fails (non-zero exit), STOP and report the error.

Step 2: Verify Action Triggered

Check that the GitHub Action workflow was triggered:

gh run list --workflow=claude-pr-reviewer.yml --limit=1 --json status,createdAt,event -q '.[0]'

Report the run status. If no run found, note that the action may take a moment to start or may not be configured.

Step 3: Confirm and Ask

Confirm review was triggered and provide the PR link. Review usually appears within 2-5 minutes.

STOP. You MUST use AskUserQuestion tool here.

Question: "Review triggered on PR #N. Ready to address feedback?"
Option 1: "Address review now" — Run /address-pr
Option 2: "I'll check the review first"

Use $ARGUMENTS as PR number if provided.