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

agent-github-pr-manager

Skill1 starsChanged 3 months agoMITView on GitHub

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

  • Commits and pushes

5 other projects use a version of this.

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

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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 draft PRs for early feedback

    line 166

≈ “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 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

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.