agentleFS
Soulcynics404Soulcynics404/AgentForge/.agents/skills/agent-pr-manager/SKILL.md

agent-pr-manager

Skill1 starsChanged 3 months agoMITView on GitHub

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

  • Commits and pushes

5 other projects use a version of this, 2 of them edited.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use memory for cross-agent coordination

    line 158
  2. Distinctive:

    Use TodoWrite for PR milestone tracking

    line 171
  3. Distinctive:

    Test failures with automatic re-runs

    line 189
  4. Distinctive:

    No single point of failure

    line 193

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.