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

시작하기

pr-review

스타2

포크2

업데이트2026년 3월 13일 12:56

Scope-aware GitHub PR review with user-friendly tone and trust tier validation

설치

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

Manus에서 실행

출처

summarybotng

summarybotng/summarybot-ng

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

다운로드

Manus에서 실행

PR Review Workflow

Review pull requests with correct AQE scope boundaries, clear communication, and actionable feedback.

Arguments

<pr-number> — GitHub PR number to review. If omitted, prompt the user.

Steps

1. Read the Full Diff

gh pr diff <pr-number>
gh pr view <pr-number>

Read the complete diff and PR description. Do not skim — read every changed file.

2. Scope Check

Only analyze AQE/QE skills (NOT Claude Flow platform skills)
Platform skills to EXCLUDE: v3-, flow-nexus-, agentdb-, reasoningbank-, swarm-, github-, hive-mind-advanced, hooks-automation, iterative-loop, stream-chain, skill-builder, sparc-methodology, pair-programming, release, debug-loop, aqe-v2-v3-migration
If the PR touches skills, verify the count/scope matches expectations (~78 AQE skills)
Flag any platform skill changes that may have leaked into an AQE-focused PR

3. Summarize Changes

Write a user-friendly summary of what changed and why:

Focus on outcomes, not implementation details
Avoid overly technical jargon
Keep it to 3-5 bullet points

4. Trust Tier Validation

For any skill changes, validate trust_tier assignments:

tier 3 = has eval infrastructure (evals/, schemas/, scripts/)
tier 2 = tested but no eval framework
tier 1 = untested
Flag inconsistencies (e.g., a skill with evals at tier 2 should be tier 3)

5. Code Quality Review

Check for:

Hardcoded version strings
Production safety concerns (adapter changes, breaking changes)
Missing test coverage for new code
Security issues (exposed secrets, injection risks)

6. Post Review

gh pr review <pr-number> --body "review comments"

Communication Rules

Keep tone constructive and actionable
Be outcome-focused: what should the author do, not what's wrong
Group related comments together instead of posting many small ones
If approving with minor suggestions, use APPROVE with comments, not REQUEST_CHANGES

이 저장소의 다른 Skills

같은 저장소

a11y-ally

summarybotng/summarybot-ng

Comprehensive WCAG accessibility auditing with multi-tool testing (axe-core + pa11y + Lighthouse), TRUE PARALLEL execution with Promise.allSettled, graceful degradation, retry with backoff, context-aware remediation, learning integration, and video accessibility. Uses 3-tier browser cascade: Vibium → agent-browser → Playwright+Stealth.

2026-03-132

accessibility-testing

summarybotng/summarybot-ng

WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.

2026-03-132

agentic-quality-engineering

summarybotng/summarybot-ng

AI agents as force multipliers for quality work. Core skill for all 19 QE agents using PACT principles.

2026-03-132

api-testing-patterns

summarybotng/summarybot-ng

Comprehensive API testing patterns including contract testing, REST/GraphQL testing, and integration testing. Use when testing APIs or designing API test strategies.

2026-03-132

aqe-v2-v3-migration

summarybotng/summarybot-ng

Migrate Agentic QE projects from v2 to v3 with zero data loss

2026-03-132

brutal-honesty-review

summarybotng/summarybot-ng

Unvarnished technical criticism combining Linus Torvalds' precision, Gordon Ramsay's standards, and James Bach's BS-detection. Use when code/tests need harsh reality checks, certification schemes smell fishy, or technical decisions lack rigor. No sugar-coating, just surgical truth about what's broken and why.

2026-03-132

name	pr-review
description	Scope-aware GitHub PR review with user-friendly tone and trust tier validation
trust_tier	0
domain	code-review

PR Review Workflow

Review pull requests with correct AQE scope boundaries, clear communication, and actionable feedback.

Arguments

<pr-number> — GitHub PR number to review. If omitted, prompt the user.

Steps

1. Read the Full Diff

gh pr diff <pr-number>
gh pr view <pr-number>

Read the complete diff and PR description. Do not skim — read every changed file.

2. Scope Check

Only analyze AQE/QE skills (NOT Claude Flow platform skills)
Platform skills to EXCLUDE: v3-, flow-nexus-, agentdb-, reasoningbank-, swarm-, github-, hive-mind-advanced, hooks-automation, iterative-loop, stream-chain, skill-builder, sparc-methodology, pair-programming, release, debug-loop, aqe-v2-v3-migration
If the PR touches skills, verify the count/scope matches expectations (~78 AQE skills)
Flag any platform skill changes that may have leaked into an AQE-focused PR

3. Summarize Changes

Write a user-friendly summary of what changed and why:

Focus on outcomes, not implementation details
Avoid overly technical jargon
Keep it to 3-5 bullet points

4. Trust Tier Validation

For any skill changes, validate trust_tier assignments:

tier 3 = has eval infrastructure (evals/, schemas/, scripts/)
tier 2 = tested but no eval framework
tier 1 = untested
Flag inconsistencies (e.g., a skill with evals at tier 2 should be tier 3)

5. Code Quality Review

Check for:

Hardcoded version strings
Production safety concerns (adapter changes, breaking changes)
Missing test coverage for new code
Security issues (exposed secrets, injection risks)

6. Post Review

gh pr review <pr-number> --body "review comments"

Communication Rules

Keep tone constructive and actionable
Be outcome-focused: what should the author do, not what's wrong
Group related comments together instead of posting many small ones
If approving with minor suggestions, use APPROVE with comments, not REQUEST_CHANGES