agent-github-modes
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: agent-github-modes
description: Agent skill for github-modes - invoke with $agent-github-modes name: github-modes description: C…
category: ai
runtime: no special runtime
---
# agent-github-modes output preview
## PART A: Task fit
- Use case: Agent skill for github-modes - invoke with $agent-github-modes name: github-modes description: Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization tools: mcpclaude-flowswarminit, mcpclaude-flowagentspawn, mcpclaude-flowtask_orchestrate, Bash, TodoWrite, Read, Write type: dev….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Overview / GitHub Workflow Modes / gh-coordinator” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for github-modes - invoke with $agent-github-modes name: github-modes description: Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization tools: mcpclaude-flowswarminit, mcpclaude-flowagentspawn, mcpclaude-flowtask_orchestrate, Bash, TodoWrite, Read, Write type: dev…”.
- **02** When the source has headings, the agent prioritizes “Overview / GitHub Workflow Modes / gh-coordinator” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Overview / GitHub Workflow Modes / gh-coordinator”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-github-modes
description: Agent skill for github-modes - invoke with $agent-github-modes name: github-modes description: C…
category: ai
source: ruvnet/ruflo
---
# agent-github-modes
## When to use
- Agent skill for github-modes - invoke with $agent-github-modes name: github-modes description: Comprehensive GitHub in…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Overview / GitHub Workflow Modes / gh-coordinator” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-github-modes" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Overview / GitHub Workflow Modes / gh-coordinator
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} 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 management
Integration Commands
sync-coordinator
Multi-package synchronization
- Package Sync: Intelligent
- Version Alignment: Automatic
- Dependency Resolution: Advanced
- Tools: git commands, gh pr create, Read, Write, Bash
- Usage:
$github sync-coordinator <sync task> - Best For: Package synchronization, version management, dependency updates
ci-orchestrator
CI/CD pipeline coordination
- Pipeline Management: Advanced
- Test Coordination: Parallel
- Deployment: Automated
- Tools: gh pr checks, gh workflow list, gh run list, Bash, TodoWrite, Task
- Usage:
$github ci-orchestrator <CI/CD task> - Best For: CI/CD coordination, test management, deployment automation
security-guardian
Security and compliance management
- Security Scan: Automated
- Compliance Check: Continuous
- Vulnerability Management: Proactive
- Tools: gh search code, gh issue create, gh secret list, Read, Write
- Usage:
$github security-guardian <security task> - Best For: Security audits, compliance checks, vulnerability management
Usage Examples
Creating a coordinated pull request workflow:
$github pr-manager "Review and merge feature$new-integration branch with automated testing and multi-reviewer coordination"
Managing repository synchronization:
$github sync-coordinator "Synchronize claude-code-flow and ruv-swarm packages, align versions, and update cross-dependencies"
Setting up automated issue tracking:
$github issue-tracker "Create and manage integration issues with automated progress tracking and swarm coordination"
Batch Operations
All GitHub modes support batch operations for maximum efficiency:
Parallel GitHub Operations Example:
[Single Message with BatchTool]:
Bash("gh issue create --title 'Feature A' --body '...'")
Bash("gh issue create --title 'Feature B' --body '...'")
Bash("gh pr create --title 'PR 1' --head 'feature-a' --base 'main'")
Bash("gh pr create --title 'PR 2' --head 'feature-b' --base 'main'")
TodoWrite { todos: [todo1, todo2, todo3] }
Bash("git checkout main && git pull")
Integration with ruv-swarm
All GitHub modes can be enhanced with ruv-swarm coordination:
// Initialize swarm for GitHub workflow
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 5 }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "GitHub Coordinator" }
mcp__claude-flow__agent_spawn { type: "reviewer", name: "Code Reviewer" }
mcp__claude-flow__agent_spawn { type: "tester", name: "QA Agent" }
// Execute GitHub workflow with coordination
mcp__claude-flow__task_orchestrate { task: "GitHub workflow", strategy: "parallel" }
Decide Fit First
Design Intent
How To Use It
Boundaries And Review