원클릭으로 Manus에서 모든 스킬 실행

pr-review

스타1

포크1

업데이트2026년 3월 18일 07:21

Dual-agent GitHub PR code review. Spawns two parallel background agents: (1) a Sonnet agent that finds and fixes GitHub Copilot review comments/issues on the PR, and (2) an Opus agent that performs a comprehensive code review covering security, performance, best practices, and test coverage. Use when the user asks to "review a PR", "review pull request", "code review", shares a GitHub PR URL and wants review, or asks to "fix copilot issues" on a PR. Triggers: PR URLs, "review PR #123", "review this PR", "spawn review agents", "review team".

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

przbadu

przbadu/skills-factory

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

PR Review

Dual-agent parallel code review for GitHub Pull Requests.

Workflow

When triggered with a GitHub PR URL or PR number:

Extract the PR URL/number and repo from user input
Spawn two agents in parallel (both run_in_background: true):
- Copilot Fixer (Sonnet, rails-expert-engineer) — finds and fixes Copilot review issues
- Code Reviewer (Opus, rails-expert-engineer) — comprehensive read-only review
Report results as each agent completes

Agent 1: Copilot Fixer (Sonnet)

Prompt template:

Review the GitHub PR {PR_URL} and fix all GitHub Copilot review issues/comments.

Steps:
1. Use `gh pr view {PR_NUMBER} --repo {REPO}` to get PR details
2. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/reviews` to find Copilot reviews
3. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/comments` to find all review comments
4. Look for any comments from GitHub Copilot (author association or bot markers)
5. Read the relevant files and fix each issue Copilot flagged
6. Make the fixes in the codebase

Important: Actually implement the fixes, don't just report them.

Config: model: sonnet, subagent_type: rails-expert-engineer

Agent 2: Code Reviewer (Opus)

Prompt template:

Perform a thorough code review of GitHub PR {PR_URL}.

Steps:
1. Use `gh pr view {PR_NUMBER} --repo {REPO}` to get PR details
2. Use `gh pr diff {PR_NUMBER} --repo {REPO}` to get the full diff
3. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/files` to list changed files
4. Read any changed files that need deeper context to review properly
5. Provide a comprehensive code review covering:
   - Code quality and Rails best practices
   - Security concerns (SQL injection, XSS, auth issues)
   - Performance issues (N+1 queries, missing indexes, etc.)
   - Test coverage adequacy
   - Error handling
   - Any bugs or logic errors
   - Naming conventions and code style
6. Categorize findings by severity: CRITICAL, HIGH, MEDIUM, LOW
7. Include file paths and line numbers

This is a review-only task -- do NOT make any code changes. Just report findings.

Config: model: opus, subagent_type: rails-expert-engineer

Result Reporting

As each agent completes, summarize its results to the user:

Copilot Fixer: List each fix applied with file and description
Code Reviewer: Present findings organized by severity (CRITICAL > HIGH > MEDIUM > LOW), with missing test coverage section and actionable recommendations

After both complete, ask the user if they want to run tests or commit the Copilot fixes.

이 저장소의 다른 Skills

같은 저장소

vault

przbadu/skills-factory

Obsidian vault management suite. Use when the user mentions vault, obsidian, notes, knowledge base, or asks to capture notes, clean up, search, organize, backup, get health reports, or AI-analyze their vault. Handles all vault operations via sub-commands: capture, cleanup, health, search, organize, ai, backup, setup. Triggers on /vault, vault capture, vault cleanup, vault health, vault search, vault organize, vault ai, vault backup, vault setup, or natural language equivalents.

2026-03-281

stripe-subscription-tester

przbadu/skills-factory

Interactive Stripe subscription lifecycle tester for the ProcurementExpress (po-app) Rails app. Simulates real Stripe webhook flows in dev environment to test subscription lock/unlock behavior. Use when: "test stripe", "test subscription", "test payment flow", "test incomplete subscription", "test payment failed", "test subscription lock", "stripe test scenario", "test billing", "/stripe-subscription-tester", "simulate stripe webhook", "test parent company lock", "test child company cascade", or any request to test Stripe subscription payment flows in the local development environment.

2026-03-281

pex-approval-flows

przbadu/skills-factory

ProcurementExpress approval flow configuration. Use when creating, updating, publishing, or managing approval flows and their steps, conditions, and runs. Approval flows automate the routing of POs and invoices to the right approvers based on configurable conditions. Routes to MCP tools: list_approval_flows, get_approval_flow, create_approval_flow, update_approval_flow, delete_approval_flow, archive_approval_flow, publish_approval_flow, unpublish_approval_flow, list_approval_flow_runs, get_approval_flow_entity, list_approval_flow_versions, get_approval_flow_version_details, rerun_approval_flows. Triggers on: approval flow, approval workflow, approval steps, approval conditions, approval routing, publish flow, flow runs, flow version, flow history, rerun approval.

2026-03-231

pex-auth

przbadu/skills-factory

ProcurementExpress authentication and user profile management. Use when authenticating to the ProcurementExpress API (V1 static token or V3 OAuth2 login), validating or revoking tokens, or managing the current user's profile. Routes to MCP tools: authenticate, validate_token, revoke_token, get_current_user, update_current_user. Triggers on: login, sign in, authenticate, token, session, user profile, my account, change password.

2026-03-231

pex-budgets

przbadu/skills-factory

ProcurementExpress budget management. Use when listing, viewing, creating, or updating budgets (cost centers). Routes to MCP tools: list_budgets, get_budget, create_budget, update_budget. Triggers on: budget, cost center, spending limit, budget allocation, remaining budget, budget approvers.

2026-03-231

pex-companies

przbadu/skills-factory

ProcurementExpress company management, employee listing, user invitations, and approver queries. Use when listing companies, switching the active company, viewing company details and settings, managing employees and user invitations, or querying approvers. Routes to MCP tools: list_companies, get_company, get_company_details, set_active_company, list_approvers, list_all_approvers, list_employees, invite_user, get_invite_limit, list_pending_invites, cancel_invite, resend_invite. Triggers on: company, switch company, employees, invite user, approvers, company settings, custom fields, payment terms.

2026-03-231

name

pr-review

description

PR Review

Dual-agent parallel code review for GitHub Pull Requests.

Workflow

When triggered with a GitHub PR URL or PR number:

Extract the PR URL/number and repo from user input
Spawn two agents in parallel (both run_in_background: true):
- Copilot Fixer (Sonnet, rails-expert-engineer) — finds and fixes Copilot review issues
- Code Reviewer (Opus, rails-expert-engineer) — comprehensive read-only review
Report results as each agent completes

Agent 1: Copilot Fixer (Sonnet)

Prompt template:

Review the GitHub PR {PR_URL} and fix all GitHub Copilot review issues/comments.

Steps:
1. Use `gh pr view {PR_NUMBER} --repo {REPO}` to get PR details
2. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/reviews` to find Copilot reviews
3. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/comments` to find all review comments
4. Look for any comments from GitHub Copilot (author association or bot markers)
5. Read the relevant files and fix each issue Copilot flagged
6. Make the fixes in the codebase

Important: Actually implement the fixes, don't just report them.

Config: model: sonnet, subagent_type: rails-expert-engineer

Agent 2: Code Reviewer (Opus)

Prompt template:

Perform a thorough code review of GitHub PR {PR_URL}.

Steps:
1. Use `gh pr view {PR_NUMBER} --repo {REPO}` to get PR details
2. Use `gh pr diff {PR_NUMBER} --repo {REPO}` to get the full diff
3. Use `gh api repos/{REPO}/pulls/{PR_NUMBER}/files` to list changed files
4. Read any changed files that need deeper context to review properly
5. Provide a comprehensive code review covering:
   - Code quality and Rails best practices
   - Security concerns (SQL injection, XSS, auth issues)
   - Performance issues (N+1 queries, missing indexes, etc.)
   - Test coverage adequacy
   - Error handling
   - Any bugs or logic errors
   - Naming conventions and code style
6. Categorize findings by severity: CRITICAL, HIGH, MEDIUM, LOW
7. Include file paths and line numbers

This is a review-only task -- do NOT make any code changes. Just report findings.

Config: model: opus, subagent_type: rails-expert-engineer

Result Reporting

As each agent completes, summarize its results to the user:

Copilot Fixer: List each fix applied with file and description
Code Reviewer: Present findings organized by severity (CRITICAL > HIGH > MEDIUM > LOW), with missing test coverage section and actionable recommendations

After both complete, ask the user if they want to run tests or commit the Copilot fixes.