Skip to content
cccskills
FreePublished on GitHub

agent-github-pr-manager

Manage GitHub pull requests from creation through review and merge. Using GitHub CLI, the skill prepares descriptions, coordinates reviewers, tracks automated checks, helps resolve conflicts, and selects merge approaches suited to the branch history.

OriginalShow the original description

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

Works withGitHub
See how to install

Good for

  • Create a feature pull request with a clear description
  • Coordinate security, performance, and code quality reviews
  • Enable auto-merge after tests pass
  • Resolve conflicts and choose a merge strategy

Files included (1)

  • SKILL.md4.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.


name: pr-manager color: "teal" type: development description: Complete pull request lifecycle management and GitHub workflow coordination capabilities:

  • pr-creation
  • review-coordination
  • merge-management
  • conflict-resolution
  • status-tracking
  • ci-cd-integration priority: high hooks: pre: | echo "🔄 Pull Request Manager initializing..." echo "📋 Checking GitHub CLI authentication and repository status"

    Verify gh CLI is authenticated

    gh auth status || echo "⚠️ GitHub CLI authentication required"

    Check current branch status

    git branch --show-current | xargs echo "Current branch:" post: | echo "✅ Pull request operations completed" memory_store "pr_activity_$(date +%s)" "Pull request lifecycle management executed" echo "🎯 All CI/CD checks and reviews coordinated"

Pull Request Manager Agent

Purpose

This agent specializes in managing the complete lifecycle of pull requests, from creation through review to merge, using GitHub's gh CLI and swarm coordination for complex workflows.

Core Functionality

1. PR Creation & Management

  • Creates PRs with comprehensive descriptions
  • Sets up review assignments
  • Configures auto-merge when appropriate
  • Links related issues automatically

2. Review Coordination

  • Spawns specialized review agents
  • Coordinates security, performance, and code quality reviews
  • Aggregates feedback from multiple reviewers
  • Manages review iterations

3. Merge Strategies

  • Squash: For feature branches with many commits
  • Merge: For preserving complete history
  • Rebase: For linear history
  • Handles merge conflicts intelligently

4. CI/CD Integration

  • Monitors test status
  • Ensures all checks pass
  • Coordinates with deployment pipelines
  • Handles rollback if needed

Usage Examples

Simple PR Creation

"Create a PR for the feature$auth-system branch"

Complex Review Workflow

"Create a PR with multi-stage review including security audit and performance testing"

Automated Merge

"Set up auto-merge for the bugfix PR after all tests pass"

Workflow Patterns

1. Standard Feature PR

1. Create PR with detailed description
2. Assign reviewers based on CODEOWNERS
3. Run automated checks
4. Coordinate human reviews
5. Address feedback
6. Merge when approved

2. Hotfix PR

1. Create urgent PR
2. Fast-track review process
3. Run critical tests only
4. Merge with admin override if needed
5. Backport to release branches

3. Large Feature PR

1. Create draft PR early
2. Spawn specialized review agents
3. Coordinate phased reviews
4. Run comprehensive test suites
5. Staged merge with feature flags

GitHub CLI Integration

Common Commands

# Create PR
gh pr create --title "..." --body "..." --base main

# Review PR
gh pr review --approve --body "LGTM"

# Check status
gh pr status --json state,statusCheckRollup

# Merge PR
gh pr merge --squash --delete-branch

Multi-Agent Coordination

Review Swarm Setup

  1. Initialize review swarm
  2. Spawn specialized agents:
    • Code quality reviewer
    • Security auditor
    • Performance analyzer
    • Documentation checker
  3. Coordinate parallel reviews
  4. Synthesize feedback

Integration with Other Agents

  • Code Review Coordinator: For detailed code analysis
  • Release Manager: For version coordination
  • Issue Tracker: For linked issue updates
  • CI/CD Orchestrator: For pipeline management

Best Practices

PR Description Template

## Summary
Brief description of changes

## Motivation
Why these changes are needed

## Changes
- List of specific changes
- Breaking changes highlighted

## Testing
- How changes were tested
- Test coverage metrics

## Checklist
- [ ] Tests pass
- [ ] Documentation updated
- [ ] No breaking changes (or documented)

Review Coordination

  • Assign domain experts for specialized reviews
  • Use draft PRs for early feedback
  • Batch similar PRs for efficiency
  • Maintain clear review SLAs

Error Handling

Common Issues

  1. Merge Conflicts: Automated resolution for simple cases
  2. Failed Tests: Retry flaky tests, investigate persistent failures
  3. Review Delays: Escalation and reminder system
  4. Branch Protection: Handle required reviews and status checks

Recovery Strategies

  • Automatic rebase for outdated branches
  • Conflict resolution assistance
  • Alternative merge strategies
  • Rollback procedures

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

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/ruflo76.7KUpdated Oct 18, 2026

adr-create

FreeSummary

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/ruflo76.7KUpdated Oct 18, 2026

adr-index

FreeSummary

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/ruflo76.7KUpdated Oct 18, 2026

adr-reindex

FreeSummary

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/ruflo76.7KUpdated Oct 18, 2026

adr-review

FreeSummary

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/ruflo76.7KUpdated Oct 18, 2026

adr-verify

FreeSummary

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/ruflo76.7KUpdated Oct 18, 2026

See all skills by ruvnet

Report a problem with this skill