본문으로 건너뛰기
cccskills
무료GitHub에 공개

agent-pr-manager

Manage GitHub pull requests, which are proposals to merge code changes, from creation through review, testing, conflict resolution, and merging. Coordinate multiple agents to divide review work and track progress across the process.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Agent skill for pr-manager - invoke with $agent-pr-manager

연동 도구GitHub
설치 방법 보기

이럴 때 유용합니다

  • Creating a pull request and coordinating its review
  • Dividing reviews of large changes among multiple agents
  • Checking tests, lint, and builds before merging
  • Resolving merge conflicts and synchronizing branches

포함된 파일(1)

  • SKILL.md6.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.


name: pr-manager description: Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows type: development color: "#4ECDC4" tools:

  • Bash
  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • LS
  • TodoWrite
  • mcp__claude-flow__swarm_init
  • mcp__claude-flow__agent_spawn
  • mcp__claude-flow__task_orchestrate
  • mcp__claude-flow__swarm_status
  • mcp__claude-flow__memory_usage
  • mcp__claude-flow__github_pr_manage
  • mcp__claude-flow__github_code_review
  • mcp__claude-flow__github_metrics hooks: pre:
    • "gh auth status || (echo 'GitHub CLI not authenticated' && exit 1)"
    • "git status --porcelain"
    • "gh pr list --state open --limit 1 >$dev$null || echo 'No open PRs'"
    • "npm test --silent || echo 'Tests may need attention'" post:
    • "gh pr status || echo 'No active PR in current branch'"
    • "git branch --show-current"
    • "gh pr checks || echo 'No PR checks available'"
    • "git log --oneline -3"

GitHub PR Manager

Purpose

Comprehensive pull request management with swarm coordination for automated reviews, testing, and merge workflows.

Capabilities

  • Multi-reviewer coordination with swarm agents
  • Automated conflict resolution and merge strategies
  • Comprehensive testing integration and validation
  • Real-time progress tracking with GitHub issue coordination
  • Intelligent branch management and synchronization

Usage Patterns

1. Create and Manage PR with Swarm Coordination

// Initialize review swarm
mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Code Quality Reviewer" }
mcp__claude-flow__agent_spawn { type: "tester", name: "Testing Agent" }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "PR Coordinator" }

// Create PR and orchestrate review
mcp__github__create_pull_request {
  owner: "ruvnet",
  repo: "ruv-FANN",
  title: "Integration: claude-code-flow and ruv-swarm",
  head: "integration$claude-code-flow-ruv-swarm",
  base: "main",
  body: "Comprehensive integration between packages..."
}

// Orchestrate review process
mcp__claude-flow__task_orchestrate {
  task: "Complete PR review with testing and validation",
  strategy: "parallel",
  priority: "high"
}

2. Automated Multi-File Review

// Get PR files and create parallel review tasks
mcp__github__get_pull_request_files { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54 }

// Create coordinated reviews
mcp__github__create_pull_request_review {
  owner: "ruvnet",
  repo: "ruv-FANN", 
  pull_number: 54,
  body: "Automated swarm review with comprehensive analysis",
  event: "APPROVE",
  comments: [
    { path: "package.json", line: 78, body: "Dependency integration verified" },
    { path: "src$index.js", line: 45, body: "Import structure optimized" }
  ]
}

3. Merge Coordination with Testing

// Validate PR status and merge when ready
mcp__github__get_pull_request_status { owner: "ruvnet", repo: "ruv-FANN", pull_number: 54 }

// Merge with coordination
mcp__github__merge_pull_request {
  owner: "ruvnet",
  repo: "ruv-FANN",
  pull_number: 54,
  merge_method: "squash",
  commit_title: "feat: Complete claude-code-flow and ruv-swarm integration",
  commit_message: "Comprehensive integration with swarm coordination"
}

// Post-merge coordination
mcp__claude-flow__memory_usage {
  action: "store",
  key: "pr/54$merged",
  value: { timestamp: Date.now(), status: "success" }
}

Batch Operations Example

Complete PR Lifecycle in Parallel:

[Single Message - Complete PR Management]:
  // Initialize coordination
  mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 }
  mcp__claude-flow__agent_spawn { type: "reviewer", name: "Senior Reviewer" }
  mcp__claude-flow__agent_spawn { type: "tester", name: "QA Engineer" }
  mcp__claude-flow__agent_spawn { type: "coordinator", name: "Merge Coordinator" }
  
  // Create and manage PR using gh CLI
  Bash("gh pr create --repo :owner/:repo --title '...' --head '...' --base 'main'")
  Bash("gh pr view 54 --repo :owner/:repo --json files")
  Bash("gh pr review 54 --repo :owner/:repo --approve --body '...'")
  
  
  // Execute tests and validation
  Bash("npm test")
  Bash("npm run lint")
  Bash("npm run build")
  
  // Track progress
  TodoWrite { todos: [
    { id: "review", content: "Complete code review", status: "completed" },
    { id: "test", content: "Run test suite", status: "completed" },
    { id: "merge", content: "Merge when ready", status: "pending" }
  ]}

Best Practices

1. Always Use Swarm Coordination

  • Initialize swarm before complex PR operations
  • Assign specialized agents for different review aspects
  • Use memory for cross-agent coordination

2. Batch PR Operations

  • Combine multiple GitHub API calls in single messages
  • Parallel file operations for large PRs
  • Coordinate testing and validation simultaneously

3. Intelligent Review Strategy

  • Automated conflict detection and resolution
  • Multi-agent review for comprehensive coverage
  • Performance and security validation integration

4. Progress Tracking

  • Use TodoWrite for PR milestone tracking
  • GitHub issue integration for project coordination
  • Real-time status updates through swarm memory

Integration with Other Modes

Works seamlessly with:

  • $github issue-tracker - For project coordination
  • $github branch-manager - For branch strategy
  • $github ci-orchestrator - For CI/CD integration
  • $sparc reviewer - For detailed code analysis
  • $sparc tester - For comprehensive testing

Error Handling

Automatic retry logic for:

  • Network failures during GitHub API calls
  • Merge conflicts with intelligent resolution
  • Test failures with automatic re-runs
  • Review bottlenecks with load balancing

Swarm coordination ensures:

  • No single point of failure
  • Automatic agent failover
  • Progress preservation across interruptions
  • Comprehensive error reporting and recovery

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

adr-index

무료

Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7만2026년 10월 19일 업데이트

ruvnet의 스킬 모두 보기

이 스킬의 문제 신고