claude-flow-novice 2.10.8 → 2.11.0

package/claude-assets/commands/github/github-modes.md

@@ -1,147 +0,0 @@
-# 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:
-```bash
-/github pr-manager "Review and merge feature/new-integration branch with automated testing and multi-reviewer coordination"
-```
-
-### Managing repository synchronization:
-```bash
-/github sync-coordinator "Synchronize claude-code-flow and ruv-swarm packages, align versions, and update cross-dependencies"
-```
-
-### Setting up automated issue tracking:
-```bash
-/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:
-```javascript
-[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:
-
-```javascript
-// 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" }
-```

package/claude-assets/commands/github/github-swarm.md

@@ -1,121 +0,0 @@
-# github swarm
-
-Create a specialized swarm for GitHub repository management.
-
-## Usage
-
-```bash
-npx claude-flow-novice github swarm [options]
-```
-
-## Options
-
-- `--repository, -r <owner/repo>` - Target GitHub repository
-- `--agents, -a <number>` - Number of specialized agents (default: 5)
-- `--focus, -f <type>` - Focus area: maintenance, development, review, triage
-- `--auto-pr` - Enable automatic pull request enhancements
-- `--issue-labels` - Auto-categorize and label issues
-- `--code-review` - Enable AI-powered code reviews
-
-## Examples
-
-### Basic GitHub swarm
-
-```bash
-npx claude-flow-novice github swarm --repository owner/repo
-```
-
-### Maintenance-focused swarm
-
-```bash
-npx claude-flow-novice github swarm -r owner/repo -f maintenance --issue-labels
-```
-
-### Development swarm with PR automation
-
-```bash
-npx claude-flow-novice github swarm -r owner/repo -f development --auto-pr --code-review
-```
-
-### Full-featured triage swarm
-
-```bash
-npx claude-flow-novice github swarm -r owner/repo -a 8 -f triage --issue-labels --auto-pr
-```
-
-## Agent Types
-
-### Issue Triager
-
-- Analyzes and categorizes issues
-- Suggests labels and priorities
-- Identifies duplicates and related issues
-
-### PR Reviewer
-
-- Reviews code changes
-- Suggests improvements
-- Checks for best practices
-
-### Documentation Agent
-
-- Updates README files
-- Creates API documentation
-- Maintains changelog
-
-### Test Agent
-
-- Identifies missing tests
-- Suggests test cases
-- Validates test coverage
-
-### Security Agent
-
-- Scans for vulnerabilities
-- Reviews dependencies
-- Suggests security improvements
-
-## Workflows
-
-### Issue Triage Workflow
-
-1. Scan all open issues
-2. Categorize by type and priority
-3. Apply appropriate labels
-4. Suggest assignees
-5. Link related issues
-
-### PR Enhancement Workflow
-
-1. Analyze PR changes
-2. Suggest missing tests
-3. Improve documentation
-4. Format code consistently
-5. Add helpful comments
-
-### Repository Health Check
-
-1. Analyze code quality metrics
-2. Review dependency status
-3. Check test coverage
-4. Assess documentation completeness
-5. Generate health report
-
-## Integration with Claude Code
-
-Use in Claude Code with MCP tools:
-
-```javascript
-mcp__claude-flow__github_swarm {
-  repository: "owner/repo",
-  agents: 6,
-  focus: "maintenance"
-}
-```
-
-## See Also
-
-- `repo analyze` - Deep repository analysis
-- `pr enhance` - Enhance pull requests
-- `issue triage` - Intelligent issue management
-- `code review` - Automated reviews

package/claude-assets/commands/github/issue-tracker.md

@@ -1,292 +0,0 @@
-# GitHub Issue Tracker
-
-## Purpose
-Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
-
-## Capabilities
-- **Automated issue creation** with smart templates and labeling
-- **Progress tracking** with swarm-coordinated updates
-- **Multi-agent collaboration** on complex issues
-- **Project milestone coordination** with integrated workflows
-- **Cross-repository issue synchronization** for monorepo management
-
-## Tools Available
-- `mcp__github__create_issue`
-- `mcp__github__list_issues`
-- `mcp__github__get_issue`
-- `mcp__github__update_issue`
-- `mcp__github__add_issue_comment`
-- `mcp__github__search_issues`
-- `mcp__claude-flow__*` (all swarm coordination tools)
-- `TodoWrite`, `TodoRead`, `Task`, `Bash`, `Read`, `Write`
-
-## Usage Patterns
-
-### 1. Create Coordinated Issue with Swarm Tracking
-```javascript
-// Initialize issue management swarm
-mcp__claude-flow__swarm_init { topology: "star", maxAgents: 3 }
-mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Coordinator" }
-mcp__claude-flow__agent_spawn { type: "researcher", name: "Requirements Analyst" }
-mcp__claude-flow__agent_spawn { type: "coder", name: "Implementation Planner" }
-
-// Create comprehensive issue
-mcp__github__create_issue {
-  owner: "ruvnet",
-  repo: "ruv-FANN",
-  title: "Integration Review: claude-code-flow and ruv-swarm complete integration",
-  body: `## 🔄 Integration Review
-  
-  ### Overview
-  Comprehensive review and integration between packages.
-  
-  ### Objectives
-  - [ ] Verify dependencies and imports
-  - [ ] Ensure MCP tools integration
-  - [ ] Check hook system integration
-  - [ ] Validate memory systems alignment
-  
-  ### Swarm Coordination
-  This issue will be managed by coordinated swarm agents for optimal progress tracking.`,
-  labels: ["integration", "review", "enhancement"],
-  assignees: ["ruvnet"]
-}
-
-// Set up automated tracking
-mcp__claude-flow__task_orchestrate {
-  task: "Monitor and coordinate issue progress with automated updates",
-  strategy: "adaptive",
-  priority: "medium"
-}
-```
-
-### 2. Automated Progress Updates
-```javascript
-// Update issue with progress from swarm memory
-mcp__claude-flow__memory_usage {
-  action: "retrieve",
-  key: "issue/54/progress"
-}
-
-// Add coordinated progress comment
-mcp__github__add_issue_comment {
-  owner: "ruvnet",
-  repo: "ruv-FANN",
-  issue_number: 54,
-  body: `## 🚀 Progress Update
-
-  ### Completed Tasks
-  - ✅ Architecture review completed (agent-1751574161764)
-  - ✅ Dependency analysis finished (agent-1751574162044)
-  - ✅ Integration testing verified (agent-1751574162300)
-  
-  ### Current Status
-  - 🔄 Documentation review in progress
-  - 📊 Integration score: 89% (Excellent)
-  
-  ### Next Steps
-  - Final validation and merge preparation
-  
-  ---
-  🤖 Generated with Claude Code using ruv-swarm coordination`
-}
-
-// Store progress in swarm memory
-mcp__claude-flow__memory_usage {
-  action: "store",
-  key: "issue/54/latest_update",
-  value: { timestamp: Date.now(), progress: "89%", status: "near_completion" }
-}
-```
-
-### 3. Multi-Issue Project Coordination
-```javascript
-// Search and coordinate related issues
-mcp__github__search_issues {
-  q: "repo:ruvnet/ruv-FANN label:integration state:open",
-  sort: "created",
-  order: "desc"
-}
-
-// Create coordinated issue updates
-mcp__github__update_issue {
-  owner: "ruvnet",
-  repo: "ruv-FANN",
-  issue_number: 54,
-  state: "open",
-  labels: ["integration", "review", "enhancement", "in-progress"],
-  milestone: 1
-}
-```
-
-## Batch Operations Example
-
-### Complete Issue Management Workflow:
-```javascript
-[Single Message - Issue Lifecycle Management]:
-  // Initialize issue coordination swarm
-  mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 }
-  mcp__claude-flow__agent_spawn { type: "coordinator", name: "Issue Manager" }
-  mcp__claude-flow__agent_spawn { type: "analyst", name: "Progress Tracker" }
-  mcp__claude-flow__agent_spawn { type: "researcher", name: "Context Gatherer" }
-  
-  // Create multiple related issues using gh CLI
-  Bash(`gh issue create \
-    --repo :owner/:repo \
-    --title "Feature: Advanced GitHub Integration" \
-    --body "Implement comprehensive GitHub workflow automation..." \
-    --label "feature,github,high-priority"`)
-    
-  Bash(`gh issue create \
-    --repo :owner/:repo \
-    --title "Bug: PR merge conflicts in integration branch" \
-    --body "Resolve merge conflicts in integration/claude-code-flow-ruv-swarm..." \
-    --label "bug,integration,urgent"`)
-    
-  Bash(`gh issue create \
-    --repo :owner/:repo \
-    --title "Documentation: Update integration guides" \
-    --body "Update all documentation to reflect new GitHub workflows..." \
-    --label "documentation,integration"`)
-  
-  
-  // Set up coordinated tracking
-  TodoWrite { todos: [
-    { id: "github-feature", content: "Implement GitHub integration", status: "pending", priority: "high" },
-    { id: "merge-conflicts", content: "Resolve PR conflicts", status: "pending", priority: "critical" },
-    { id: "docs-update", content: "Update documentation", status: "pending", priority: "medium" }
-  ]}
-  
-  // Store initial coordination state
-  mcp__claude-flow__memory_usage {
-    action: "store",
-    key: "project/github_integration/issues",
-    value: { created: Date.now(), total_issues: 3, status: "initialized" }
-  }
-```
-
-## Smart Issue Templates
-
-### Integration Issue Template:
-```markdown
-## 🔄 Integration Task
-
-### Overview
-[Brief description of integration requirements]
-
-### Objectives
-- [ ] Component A integration
-- [ ] Component B validation  
-- [ ] Testing and verification
-- [ ] Documentation updates
-
-### Integration Areas
-#### Dependencies
-- [ ] Package.json updates
-- [ ] Version compatibility
-- [ ] Import statements
-
-#### Functionality  
-- [ ] Core feature integration
-- [ ] API compatibility
-- [ ] Performance validation
-
-#### Testing
-- [ ] Unit tests
-- [ ] Integration tests
-- [ ] End-to-end validation
-
-### Swarm Coordination
-- **Coordinator**: Overall progress tracking
-- **Analyst**: Technical validation
-- **Tester**: Quality assurance
-- **Documenter**: Documentation updates
-
-### Progress Tracking
-Updates will be posted automatically by swarm agents during implementation.
-
----
-🤖 Generated with Claude Code
-```
-
-### Bug Report Template:
-```markdown
-## 🐛 Bug Report
-
-### Problem Description
-[Clear description of the issue]
-
-### Expected Behavior
-[What should happen]
-
-### Actual Behavior  
-[What actually happens]
-
-### Reproduction Steps
-1. [Step 1]
-2. [Step 2]
-3. [Step 3]
-
-### Environment
-- Package: [package name and version]
-- Node.js: [version]
-- OS: [operating system]
-
-### Investigation Plan
-- [ ] Root cause analysis
-- [ ] Fix implementation
-- [ ] Testing and validation
-- [ ] Regression testing
-
-### Swarm Assignment
-- **Debugger**: Issue investigation
-- **Coder**: Fix implementation
-- **Tester**: Validation and testing
-
----
-🤖 Generated with Claude Code
-```
-
-## Best Practices
-
-### 1. **Swarm-Coordinated Issue Management**
-- Always initialize swarm for complex issues
-- Assign specialized agents based on issue type
-- Use memory for progress coordination
-
-### 2. **Automated Progress Tracking**
-- Regular automated updates with swarm coordination
-- Progress metrics and completion tracking
-- Cross-issue dependency management
-
-### 3. **Smart Labeling and Organization**
-- Consistent labeling strategy across repositories
-- Priority-based issue sorting and assignment
-- Milestone integration for project coordination
-
-### 4. **Batch Issue Operations**
-- Create multiple related issues simultaneously
-- Bulk updates for project-wide changes
-- Coordinated cross-repository issue management
-
-## Integration with Other Modes
-
-### Seamless integration with:
-- `/github pr-manager` - Link issues to pull requests
-- `/github release-manager` - Coordinate release issues
-- `/sparc orchestrator` - Complex project coordination
-- `/sparc tester` - Automated testing workflows
-
-## Metrics and Analytics
-
-### Automatic tracking of:
-- Issue creation and resolution times
-- Agent productivity metrics
-- Project milestone progress
-- Cross-repository coordination efficiency
-
-### Reporting features:
-- Weekly progress summaries
-- Agent performance analytics
-- Project health metrics
-- Integration success rates

package/claude-assets/commands/github/issue-triage.md

@@ -1,25 +0,0 @@
-# issue-triage
-
-Intelligent issue classification and triage.
-
-## Usage
-```bash
-npx claude-flow-novice github issue-triage [options]
-```
-
-## Options
-- `--repository <owner/repo>` - Target repository
-- `--auto-label` - Automatically apply labels
-- `--assign` - Auto-assign to team members
-
-## Examples
-```bash
-# Triage issues
-npx claude-flow-novice github issue-triage --repository myorg/myrepo
-
-# With auto-labeling
-npx claude-flow-novice github issue-triage --repository myorg/myrepo --auto-label
-
-# Full automation
-npx claude-flow-novice github issue-triage --repository myorg/myrepo --auto-label --assign
-```