agentleFS
fidgetcodingfidgetcoding/fidgetflo/.agents/skills/agent-github-modes/SKILL.md

agent-github-modes

Skill1 starsChanged 7 months agoMITView on GitHub

Agent skill for github-modes - invoke with $agent-github-modes

  • Commits and pushes

5 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 2 are common, 0 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    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. Common:

    All GitHub modes support batch operations for maximum efficiency:

    line 152
  2. Common:

    All GitHub modes can be enhanced with ruv-swarm coordination:

    line 167

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “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: github-modes description: Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization tools: mcp__fidgetflo__swarm_init, mcp__fidgetflo__agent_spawn, mcp__fidgetflo__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 FidgetFlo 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__fidgetflo__swarm_init { topology: "hierarchical", maxAgents: 5 }
mcp__fidgetflo__agent_spawn { type: "coordinator", name: "GitHub Coordinator" }
mcp__fidgetflo__agent_spawn { type: "reviewer", name: "Code Reviewer" }
mcp__fidgetflo__agent_spawn { type: "tester", name: "QA Agent" }

// Execute GitHub workflow with coordination
mcp__fidgetflo__task_orchestrate { task: "GitHub workflow", strategy: "parallel" }

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.