Restructured project from nested workspace pattern to flat single-repo layout. This eliminates redundant nesting and consolidates all project files under version control. ## Migration Summary **Before:** ``` alex/ (workspace, not versioned) ├── chess-game/ (git repo) │ ├── js/, css/, tests/ │ └── index.html └── docs/ (planning, not versioned) ``` **After:** ``` alex/ (git repo, everything versioned) ├── js/, css/, tests/ ├── index.html ├── docs/ (project documentation) ├── planning/ (historical planning docs) ├── .gitea/ (CI/CD) └── CLAUDE.md (configuration) ``` ## Changes Made ### Structure Consolidation - Moved all chess-game/ contents to root level - Removed redundant chess-game/ subdirectory - Flattened directory structure (eliminated one nesting level) ### Documentation Organization - Moved chess-game/docs/ → docs/ (project documentation) - Moved alex/docs/ → planning/ (historical planning documents) - Added CLAUDE.md (workspace configuration) - Added IMPLEMENTATION_PROMPT.md (original project prompt) ### Version Control Improvements - All project files now under version control - Planning documents preserved in planning/ folder - Merged .gitignore files (workspace + project) - Added .claude/ agent configurations ### File Updates - Updated .gitignore to include both workspace and project excludes - Moved README.md to root level - All import paths remain functional (relative paths unchanged) ## Benefits ✅ **Simpler Structure** - One level of nesting removed ✅ **Complete Versioning** - All documentation now in git ✅ **Standard Layout** - Matches open-source project conventions ✅ **Easier Navigation** - Direct access to all project files ✅ **CI/CD Compatible** - All workflows still functional ## Technical Validation - ✅ Node.js environment verified - ✅ Dependencies installed successfully - ✅ Dev server starts and responds - ✅ All core files present and accessible - ✅ Git repository functional ## Files Preserved **Implementation Files:** - js/ (3,517 lines of code) - css/ (4 stylesheets) - tests/ (87 test cases) - index.html - package.json **CI/CD Pipeline:** - .gitea/workflows/ci.yml - .gitea/workflows/release.yml **Documentation:** - docs/ (12+ documentation files) - planning/ (historical planning materials) - README.md **Configuration:** - jest.config.js, babel.config.cjs, playwright.config.js - .gitignore (merged) - CLAUDE.md 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
6.5 KiB
6.5 KiB
name, description, tools, color, type, capabilities, priority, hooks
| name | description | tools | color | type | capabilities | priority | hooks | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github-modes | Comprehensive GitHub integration modes for workflow orchestration, PR management, and repository coordination with batch optimization | mcp__claude-flow__swarm_init, mcp__claude-flow__agent_spawn, mcp__claude-flow__task_orchestrate, Bash, TodoWrite, Read, Write | purple | development |
|
medium |
|
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" }