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
Most recently taken up by
- ruvnet/rufloword for word, first seen Oct 21, 2026
- ruvnet/claude-flowword for word, first seen Oct 8, 2026
- jpoindexter/theft-kitword for word, first seen May 20, 2026
- fidgetcoding/fidgetfloword for word, first seen Apr 17, 2026
- Zekiog/rufloword for word, first seen Apr 8, 2026
Other versions5 projects use a version of this.
Word for word · 5
- ruvnet/claude-flow★ 80k100% same
- ruvnet/ruflo★ 79k100% same
- Zekiog/ruflo★ 2100% same
- fidgetcoding/fidgetflo★ 1100% same
- jpoindexter/theft-kit★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository176 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/commands/monitoring/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- v3/CLAUDE.mdCLAUDE.md
- agent-adaptive-coordinatorSkill
- agent-agentic-paymentsSkill
- agent-agentSkill
- agent-analyze-code-qualitySkill
- agent-app-storeSkill
- agent-architectureSkill
- agent-arch-system-designSkill
- agent-authenticationSkill
- agent-automation-smart-agentSkill
- agent-base-template-generatorSkill
- agent-benchmark-suiteSkill
- agent-byzantine-coordinatorSkill
- agent-challengesSkill
- agent-code-analyzerSkill
- agent-code-goal-plannerSkill
- agent-code-review-swarmSkill
- agent-coderSkill
- agent-collective-intelligence-coordinatorSkill
- agent-consensus-coordinatorSkill
- agent-coordinationSkill
- agent-coordinator-swarm-initSkill
- agent-crdt-synchronizerSkill
- agent-data-ml-modelSkill
- AgentDB Advanced FeaturesSkill
- AgentDB Learning PluginsSkill
- AgentDB Memory PatternsSkill
- AgentDB Performance OptimizationSkill
- AgentDB Vector SearchSkill
- agent-dev-backend-apiSkill
- agent-docs-api-openapiSkill
- agent-github-modesSkill
- agent-goal-plannerSkill
- agent-gossip-coordinatorSkill
- agent-hierarchical-coordinatorSkill
- agentic-jujutsuSkill
- agent-implementer-sparc-coderSkill
- agent-issue-trackerSkill
- agent-load-balancerSkill
- agent-matrix-optimizerSkill
- agent-memory-coordinatorSkill
- agent-mesh-coordinatorSkill
- agent-migration-planSkill
- agent-multi-repo-swarmSkill
- agent-neural-networkSkill
- agent-ops-cicd-githubSkill
- agent-orchestrator-taskSkill
- agent-pagerank-analyzerSkill
- agent-paymentsSkill
- agent-performance-analyzerSkill
- agent-performance-benchmarkerSkill
- agent-performance-monitorSkill
- agent-performance-optimizerSkill
- agent-plannerSkill
- agent-pr-managerSkill
- agent-production-validatorSkill
- agent-project-board-syncSkill
- The first 60 shown.
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
- Distinctive: line 166
Use draft PRs for early feedback
≈ “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.
Files
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 approved2. 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 branches3. 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 flagsGitHub 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-branchMulti-Agent Coordination
Review Swarm Setup
- Initialize review swarm
- Spawn specialized agents:
- Code quality reviewer
- Security auditor
- Performance analyzer
- Documentation checker
- Coordinate parallel reviews
- 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
- Merge Conflicts: Automated resolution for simple cases
- Failed Tests: Retry flaky tests, investigate persistent failures
- Review Delays: Escalation and reminder system
- Branch Protection: Handle required reviews and status checks
Recovery Strategies
- Automatic rebase for outdated branches
- Conflict resolution assistance
- Alternative merge strategies
- Rollback procedures
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
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.

