Agent Github Modes
Orchestrate GitHub workflows—PRs, issues, releases, and repo coordination—from your coding agent with gh CLI and Claude-Flow swarm tools.
Overview
agent-github-modes is an agent skill most often used in Build (also Ship review, Ship launch) that runs coordinated GitHub workflow modes—PR, issue, release, and CI/CD—with gh CLI and Claude-Flow orchestration.
Install
npx skills add https://github.com/ruvnet/ruflo --skill agent-github-modesWhat is this skill?
- Named GitHub modes including gh-coordinator for hierarchical workflow orchestration
- Pull request management, issue tracking, release management, and CI/CD pipeline coordination
- Pre-hooks verify gh auth and git repo context before batch tool runs
- Claude-Flow MCP swarm_init, agent_spawn, and task_orchestrate for parallel GitHub work
- Batch-optimized patterns for repository architecture and organization
Adoption & trust: 642 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need repeatable GitHub PR, issue, and release workflows from your agent without re-explaining gh commands and swarm setup every session.
Who is it for?
Indie builders on real git repos who already use gh and Claude-Flow (or ruv-swarm) and want batch PR/issue/release coordination from the agent.
Skip if: Greenfield projects with no GitHub remote, teams that forbid agents from shell/git/API access, or workflows that only need local commits without GitHub.
When should I use this skill?
Invoke with $agent-github-modes when you need comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization.
What do I get? / Deliverables
After invocation, GitHub operations run through documented modes with auth and repo checks, swarm coordination, and synchronized post-run status so you can continue review or release steps in the same repo.
- Synchronized GitHub workflow operations per selected mode
- Post-hook confirmation of repo and workflow coordination state
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
GitHub is the canonical integration surface while you are building and wiring repo automation; the same modes carry into ship and operate. integrations fits because the skill centers on GitHub API/CLI wiring and multi-mode workflow hooks rather than pure local git aliases.
Where it fits
Stand up gh-coordinator mode so spawned agents open PRs and track issues against your main repo.
Run PR management modes to batch review comments and status checks before merge.
Coordinate release management and deployment-related GitHub workflows from one agent session.
Keep issue tracking and CI/CD pipeline coordination in sync after shipping.
How it compares
Use instead of ad-hoc gh one-liners in chat when you want named modes, hooks, and swarm batching for the same repo operations.
Common Questions / FAQ
Who is agent-github-modes for?
Solo and indie developers shipping with agentic IDEs who manage code on GitHub and want orchestrated PR, issue, and release workflows rather than manual CLI copy-paste.
When should I use agent-github-modes?
During Build when wiring GitHub integrations and repo automation; during Ship when reviewing or preparing releases and CI/CD coordination; and during Operate when syncing ongoing issue and workflow state from the agent.
Is agent-github-modes safe to install?
The skill expects gh auth, git access, Bash, and network/API use—review the Security Audits panel on this Prism page and your org’s agent permissions before enabling it on production repos.
SKILL.md
READMESKILL.md - Agent Github Modes
--- name: github-modes description: Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization tools: mcp__claude-flow__swarm_init, mcp__claude-flow__agent_spawn, mcp__claude-flow__task_orchestrate, Bash, TodoWrite, Read, Write color: purple type: development capabilities: - GitHub workflow orchestration - Pull request management and review - Issue tracking and coordination - Release management and deployment - Repository architecture and organization - CI/CD pipeline coordination priority: medium hooks: pre: | echo "Starting github-modes..." echo "Initializing GitHub workflow coordination" gh auth status || (echo "GitHub CLI authentication required" && exit 1) git status > $dev$null || (echo "Not in a git repository" && exit 1) post: | echo "Completed github-modes" echo "GitHub operations synchronized" echo "Workflow coordination finalized" --- # GitHub Integration Modes ## Overview This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency. ## GitHub Workflow Modes ### gh-coordinator **GitHub workflow orchestration and coordination** - **Coordination Mode**: Hierarchical - **Max Parallel Operations**: 10 - **Batch Optimized**: Yes - **Tools**: gh CLI commands, TodoWrite, TodoRead, Task, Memory, Bash - **Usage**: `$github gh-coordinator <GitHub workflow description>` - **Best For**: Complex GitHub workflows, multi-repo coordination ### pr-manager **Pull request management and review coordination** - **Review Mode**: Automated - **Multi-reviewer**: Yes - **Conflict Resolution**: Intelligent - **Tools**: gh pr create, gh pr view, gh pr review, gh pr merge, TodoWrite, Task - **Usage**: `$github pr-manager <PR management task>` - **Best For**: PR reviews, merge coordination, conflict resolution ### issue-tracker **Issue management and project coordination** - **Issue Workflow**: Automated - **Label Management**: Smart - **Progress Tracking**: Real-time - **Tools**: gh issue create, gh issue edit, gh issue comment, gh issue list, TodoWrite - **Usage**: `$github issue-tracker <issue management task>` - **Best For**: Project management, issue coordination, progress tracking ### release-manager **Release coordination and deployment** - **Release Pipeline**: Automated - **Versioning**: Semantic - **Deployment**: Multi-stage - **Tools**: gh pr create, gh pr merge, gh release create, Bash, TodoWrite - **Usage**: `$github release-manager <release task>` - **Best For**: Release management, version coordination, deployment pipelines ## Repository Management Modes ### repo-architect **Repository structure and organization** - **Structure Optimization**: Yes - **Multi-repo**: Support - **Template Management**: Advanced - **Tools**: gh repo create, gh repo clone, git commands, Write, Read, Bash - **Usage**: `$github repo-architect <repository management task>` - **Best For**: Repository setup, structure optimization, multi-repo management ### code-reviewer **Automated code review and quality assurance** - **Review Quality**: Deep - **Security Analysis**: Yes - **Performance Check**: Automated - **Tools**: gh pr view --json files, gh pr review, gh pr comment, Read, Write - **Usage**: `$github code-reviewer <review task>` - **Best For**: Code quality, security reviews, performance analysis ### branch-manager **Branch management and workflow coordination** - **Branch Strategy**: GitFlow - **Merge Strategy**: Intelligent - **Conflict Prevention**: Proactive - **Tools**: gh api (for branch operations), git commands, Bash - **Usage**: `$github branch-manager <branch management task>` - **Best For**: Branch coordination, merge strategies, workflow managemen