monomind 2.7.12 → 2.7.13

package/packages/@monomind/cli/.claude/commands/github/repo-architect.md

@@ -1,372 +0,0 @@
----
-name: github:repo-architect
----
-
-# GitHub Repository Architect
-
-## Purpose
-
-Repository structure optimization and multi-repo management with Monomind swarm coordination for scalable project architecture and development workflows.
-
-## Capabilities
-
-- **Repository structure optimization** with best practices
-- **Multi-repository coordination** and synchronization
-- **Template management** for consistent project setup
-- **Architecture analysis** and improvement recommendations
-- **Cross-repo workflow** coordination and management
-
-## Tools Available
-
-- `mcp__github__create_repository`
-- `mcp__github__fork_repository`
-- `mcp__github__search_repositories`
-- `mcp__github__push_files`
-- `mcp__github__create_or_update_file`
-- `mcp__monomind__*` (all swarm coordination tools)
-- `TodoWrite`, `TodoRead`, `Task`, `Bash`, `Read`, `Write`, `LS`, `Glob`
-
-## Usage Patterns
-
-### 1. Repository Structure Analysis and Optimization
-
-```javascript
-// Initialize architecture analysis swarm
-mcp__monomind__swarm_init { topology: "mesh", maxAgents: 4 }
-mcp__monomind__agent_spawn { type: "analyst", name: "Structure Analyzer" }
-mcp__monomind__agent_spawn { type: "architect", name: "Repository Architect" }
-mcp__monomind__agent_spawn { type: "optimizer", name: "Structure Optimizer" }
-mcp__monomind__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }
-
-// Analyze current repository structure
-LS(".")
-
-// Search for related repositories
-mcp__github__search_repositories {
-  query: "user::owner",
-  sort: "updated",
-  order: "desc"
-}
-
-// Orchestrate structure optimization
-mcp__monomind__coordination_orchestrate {
-  task: "Analyze and optimize repository structure for scalability and maintainability",
-  agents: ["analyst", "architect", "optimizer"],
-  strategy: "parallel"
-}
-```
-
-### 2. Multi-Repository Template Creation
-
-```javascript
-// Create standardized repository template
-mcp__github__create_repository {
-  name: "claude-project-template",
-  description: "Standardized template for Claude Code projects with monomind integration",
-  private: false,
-  autoInit: true
-}
-
-// Push template structure
-mcp__github__push_files {
-  owner: ":owner",
-  repo: "claude-project-template",
-  branch: "main",
-  files: [
-    {
-      path: ".claude/commands/github/github-modes.md",
-      content: "[GitHub modes template]"
-    },
-    {
-      path: ".claude/commands/mastermind/help.md",
-      content: "[Mastermind commands template]"
-    },
-    {
-      path: ".claude/config.json",
-      content: JSON.stringify({
-        version: "1.0",
-        mcp_servers: {
-          "monomind": {
-            command: "npx",
-            args: ["monomind", "mcp", "start"],
-            stdio: true
-          }
-        },
-        hooks: {
-          pre_task: "npx monomind hooks pre-task",
-          post_edit: "npx monomind hooks post-edit",
-          notification: "npx monomind hooks notify"
-        }
-      }, null, 2)
-    },
-    {
-      path: "CLAUDE.md",
-      content: "[Standardized CLAUDE.md template]"
-    },
-    {
-      path: "package.json",
-      content: JSON.stringify({
-        name: "claude-project-template",
-        version: "1.0.0",
-        description: "Claude Code project with monomind integration",
-        engines: { node: ">=20.0.0" },
-        dependencies: {
-          "@monomind/cli": "latest"
-        }
-      }, null, 2)
-    },
-    {
-      path: "README.md",
-      content: `# Claude Project Template
-
-## Quick Start
-\`\`\`bash
-npx monomind init
-npm install
-npx monomind start --ui
-\`\`\`
-
-## Features
-- Monomind swarm integration
-- GitHub workflow automation
-- Advanced coordination capabilities
-
-## Documentation
-See CLAUDE.md for complete integration instructions.`
-    }
-  ],
-  message: "feat: Create standardized Claude project template with Monomind integration"
-}
-```
-
-### 3. Cross-Repository Synchronization
-
-```javascript
-// Synchronize structure across related repositories
-const repositories = ["@monomind/cli", "@monoes/hooks", "@monomind/memory"];
-
-// Update common files across repositories
-repositories.forEach((repo) => {
-  mcp__github__create_or_update_file({
-    owner: "monoes",
-    repo: "monomind",
-    path: `${repo}/.github/workflows/integration.yml`,
-    content: `name: Integration Tests
-on: [push, pull_request]
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v1
-      - uses: actions/setup-node@v1
-        with: { node-version: '20' }
-      - run: npm install && npm test`,
-    message: "ci: Standardize integration workflow across repositories",
-    branch: "structure/standardization",
-  });
-});
-```
-
-## Batch Architecture Operations
-
-### Complete Repository Architecture Optimization:
-
-```javascript
-[Single Message - Repository Architecture Review]:
-  // Initialize comprehensive architecture swarm
-  mcp__monomind__swarm_init { topology: "hierarchical", maxAgents: 6 }
-  mcp__monomind__agent_spawn { type: "architect", name: "Senior Architect" }
-  mcp__monomind__agent_spawn { type: "analyst", name: "Structure Analyst" }
-  mcp__monomind__agent_spawn { type: "optimizer", name: "Performance Optimizer" }
-  mcp__monomind__agent_spawn { type: "researcher", name: "Best Practices Researcher" }
-  mcp__monomind__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }
-
-  // Analyze current repository structures
-  LS(".")
-  Read("package.json")
-
-  // Search for architectural patterns using gh CLI
-  ARCH_PATTERNS=$(Bash(`gh search repos "language:javascript template architecture" \
-    --limit 10 \
-    --json fullName,description,stargazersCount \
-    --sort stars \
-    --order desc`))
-
-  // Create optimized structure files
-  mcp__github__push_files {
-    branch: "architecture/optimization",
-    files: [
-      {
-        path: ".github/ISSUE_TEMPLATE/integration.yml",
-        content: "[Integration issue template]"
-      },
-      {
-        path: ".github/PULL_REQUEST_TEMPLATE.md",
-        content: "[Standardized PR template]"
-      },
-      {
-        path: "docs/ARCHITECTURE.md",
-        content: "[Architecture documentation]"
-      },
-      {
-        path: ".github/workflows/cross-package-test.yml",
-        content: "[Cross-package testing workflow]"
-      }
-    ],
-    message: "feat: Optimize repository architecture for scalability and maintainability"
-  }
-
-  // Track architecture improvements
-  TodoWrite { todos: [
-    { id: "arch-analysis", content: "Analyze current repository structure", status: "completed", priority: "high" },
-    { id: "arch-research", content: "Research best practices and patterns", status: "completed", priority: "medium" },
-    { id: "arch-templates", content: "Create standardized templates", status: "completed", priority: "high" },
-    { id: "arch-workflows", content: "Implement improved workflows", status: "completed", priority: "medium" },
-    { id: "arch-docs", content: "Document architecture decisions", status: "pending", priority: "medium" }
-  ]}
-
-  // Store architecture analysis
-  mcp__monomind__memory_store {
-    key: "architecture/analysis/results",
-    value: {
-      timestamp: Date.now(),
-      optimization_areas: ["structure", "workflows", "templates", "documentation"],
-      recommendations: ["standardize_structure", "improve_workflows", "enhance_templates"],
-      implementation_status: "in_progress"
-    }
-  }
-```
-
-## Architecture Patterns
-
-### 1. **Monorepo Structure Pattern**
-
-```
-monomind/
-├── packages/
-│   ├── @monomind/cli/
-│   │   ├── src/
-│   │   ├── .claude/
-│   │   └── package.json
-│   ├── @monoes/hooks/
-│   │   ├── src/
-│   │   └── package.json
-│   └── shared/
-│       ├── types/
-│       ├── utils/
-│       └── config/
-├── tools/
-│   ├── build/
-│   ├── test/
-│   └── deploy/
-├── docs/
-│   ├── architecture/
-│   ├── integration/
-│   └── examples/
-└── .github/
-    ├── workflows/
-    ├── templates/
-    └── actions/
-```
-
-### 2. **Command Structure Pattern**
-
-```
-.claude/
-├── commands/
-│   ├── github/
-│   │   ├── github-modes.md
-│   │   ├── pr-manager.md
-│   │   ├── issue-tracker.md
-│   │   └── sync-coordinator.md
-│   └── swarm/
-│       ├── coordination.md
-│       └── orchestration.md
-├── templates/
-│   ├── issue.md
-│   ├── pr.md
-│   └── project.md
-└── config.json
-```
-
-### 3. **Integration Pattern**
-
-```javascript
-const integrationPattern = {
-  packages: {
-    "@monomind/cli": {
-      role: "orchestration_layer",
-      dependencies: ["@monoes/hooks", "@monomind/memory"],
-      provides: ["CLI", "workflows", "commands"],
-    },
-    "@monoes/hooks": {
-      role: "coordination_engine",
-      dependencies: [],
-      provides: ["MCP_tools", "neural_networks", "memory"],
-    },
-  },
-  communication: "MCP_protocol",
-  coordination: "swarm_based",
-  state_management: "persistent_memory",
-};
-```
-
-## Best Practices
-
-### 1. **Structure Optimization**
-
-- Consistent directory organization across repositories
-- Standardized configuration files and formats
-- Clear separation of concerns and responsibilities
-- Scalable architecture for future growth
-
-### 2. **Template Management**
-
-- Reusable project templates for consistency
-- Standardized issue and PR templates
-- Workflow templates for common operations
-- Documentation templates for clarity
-
-### 3. **Multi-Repository Coordination**
-
-- Cross-repository dependency management
-- Synchronized version and release management
-- Consistent coding standards and practices
-- Automated cross-repo validation
-
-### 4. **Documentation Architecture**
-
-- Comprehensive architecture documentation
-- Clear integration guides and examples
-- Maintainable and up-to-date documentation
-- User-friendly onboarding materials
-
-## Monitoring and Analysis
-
-### Architecture Health Metrics:
-
-- Repository structure consistency score
-- Documentation coverage percentage
-- Cross-repository integration success rate
-- Template adoption and usage statistics
-
-### Automated Analysis:
-
-- Structure drift detection
-- Best practices compliance checking
-- Performance impact analysis
-- Scalability assessment and recommendations
-
-## Integration with Development Workflow
-
-### Seamless integration with:
-
-- `/github sync-coordinator` - For cross-repo synchronization
-- `/github release-manager` - For coordinated releases
-
-### Workflow Enhancement:
-
-- Automated structure validation
-- Continuous architecture improvement
-- Best practices enforcement
-- Documentation generation and maintenance

package/packages/@monomind/cli/.claude/commands/github/sync-coordinator.md

@@ -1,297 +0,0 @@
----
-name: github:sync-coordinator
----
-
-# GitHub Sync Coordinator
-
-## Purpose
-Multi-package synchronization and version alignment with monomind swarm coordination for seamless integration across packages.
-
-## Capabilities
-- **Package synchronization** with intelligent dependency resolution
-- **Version alignment** across multiple repositories
-- **Cross-package integration** with automated testing
-- **Documentation synchronization** for consistent user experience
-- **Release coordination** with automated deployment pipelines
-
-## Tools Available
-- `mcp__github__push_files`
-- `mcp__github__create_or_update_file`
-- `mcp__github__get_file_contents`
-- `mcp__github__create_pull_request`
-- `mcp__github__search_repositories`
-- `mcp__monomind__*` (all swarm coordination tools)
-- `TodoWrite`, `TodoRead`, `Task`, `Bash`, `Read`, `Write`, `Edit`, `MultiEdit`
-
-## Usage Patterns
-
-### 1. Synchronize Package Dependencies
-```javascript
-// Initialize sync coordination swarm
-mcp__monomind__swarm_init { topology: "hierarchical", maxAgents: 5 }
-mcp__monomind__agent_spawn { type: "coordinator", name: "Sync Coordinator" }
-mcp__monomind__agent_spawn { type: "analyst", name: "Dependency Analyzer" }
-mcp__monomind__agent_spawn { type: "coder", name: "Integration Developer" }
-mcp__monomind__agent_spawn { type: "tester", name: "Validation Engineer" }
-
-// Analyze current package states
-Read("package.json")
-
-// Synchronize versions and dependencies using gh CLI
-// First create branch
-Bash("gh api repos/:owner/:repo/git/refs -f ref='refs/heads/sync/package-alignment' -f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha')")
-
-// Update file using gh CLI
-Bash(`gh api repos/:owner/:repo/contents/packages/@monomind/cli/package.json \
-  --method PUT \
-  -f message="feat: Align Node.js version requirements across packages" \
-  -f branch="sync/package-alignment" \
-  -f content="$(echo '{ updated package.json with aligned versions }' | base64)" \
-  -f sha="$(gh api repos/:owner/:repo/contents/packages/@monomind/cli/package.json?ref=sync/package-alignment --jq '.sha')")`)
-
-// Orchestrate validation
-mcp__monomind__coordination_orchestrate {
-  task: "Validate package synchronization and run integration tests",
-  agents: ["coordinator", "analyst", "tester"],
-  strategy: "parallel"
-}
-```
-
-### 2. Documentation Synchronization
-```javascript
-// Synchronize CLAUDE.md files across packages using gh CLI
-// Get file contents
-CLAUDE_CONTENT=$(Bash("gh api repos/:owner/:repo/contents/CLAUDE.md --jq '.content' | base64 -d"))
-
-// Update package CLAUDE.md to match using gh CLI
-// Create or update branch
-Bash("gh api repos/:owner/:repo/git/refs -f ref='refs/heads/sync/documentation' -f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha') 2>/dev/null || gh api repos/:owner/:repo/git/refs/heads/sync/documentation --method PATCH -f sha=$(gh api repos/:owner/:repo/git/refs/heads/main --jq '.object.sha')")
-
-// Update file
-Bash(`gh api repos/:owner/:repo/contents/packages/@monomind/cli/CLAUDE.md \
-  --method PUT \
-  -f message="docs: Synchronize CLAUDE.md with Monomind integration patterns" \
-  -f branch="sync/documentation" \
-  -f content="$(echo '# Claude Code Configuration for Monomind\n\n[synchronized content]' | base64)" \
-  -f sha="$(gh api repos/:owner/:repo/contents/packages/@monomind/cli/CLAUDE.md?ref=sync/documentation --jq '.sha' 2>/dev/null || echo '')")`)
-
-// Store sync state in memory
-mcp__monomind__memory_store {
-  key: "sync/documentation/status",
-  value: { timestamp: Date.now(), status: "synchronized", files: ["CLAUDE.md"] }
-}
-```
-
-### 3. Cross-Package Feature Integration
-```javascript
-// Coordinate feature implementation across packages
-mcp__github__push_files {
-  owner: "monoes",
-  repo: "monomind",
-  branch: "feature/github-commands",
-  files: [
-    {
-      path: ".claude/commands/github/github-modes.md",
-      content: "[GitHub modes documentation]"
-    },
-    {
-      path: ".claude/commands/github/pr-manager.md",
-      content: "[PR manager documentation]"
-    },
-    {
-      path: "packages/@monomind/hooks/src/github-coordinator/claude-hooks.js",
-      content: "[GitHub coordination hooks]"
-    }
-  ],
-  message: "feat: Add comprehensive GitHub workflow integration"
-}
-
-// Create coordinated pull request using gh CLI
-Bash(`gh pr create \
-  --repo :owner/:repo \
-  --title "Feature: GitHub Workflow Integration with Swarm Coordination" \
-  --head "feature/github-commands" \
-  --base "main" \
-  --body "## GitHub Workflow Integration
-
-### Features Added
-- Comprehensive GitHub command modes
-- Swarm-coordinated PR management
-- Automated issue tracking
-- Cross-package synchronization
-
-### Integration Points
-- Monomind CLI: GitHub command modes in .claude/commands/github/
-- Monomind Hooks: GitHub coordination hooks and utilities
-- Documentation: Synchronized CLAUDE.md instructions
-
-### Testing
-- [x] Package dependency verification
-- [x] Integration test suite
-- [x] Documentation validation
-- [x] Cross-package compatibility
-
-### Swarm Coordination
-This integration uses Monomind swarm agents for:
-- Multi-agent GitHub workflow management
-- Automated testing and validation
-- Progress tracking and coordination
-- Memory-based state management
-
----
-Generated with Claude Code using Monomind swarm coordination`
-}
-```
-
-## Batch Synchronization Example
-
-### Complete Package Sync Workflow:
-```javascript
-[Single Message - Complete Synchronization]:
-  // Initialize comprehensive sync swarm
-  mcp__monomind__swarm_init { topology: "mesh", maxAgents: 6 }
-  mcp__monomind__agent_spawn { type: "coordinator", name: "Master Sync Coordinator" }
-  mcp__monomind__agent_spawn { type: "analyst", name: "Package Analyzer" }
-  mcp__monomind__agent_spawn { type: "coder", name: "Integration Coder" }
-  mcp__monomind__agent_spawn { type: "tester", name: "Validation Tester" }
-  mcp__monomind__agent_spawn { type: "reviewer", name: "Quality Reviewer" }
-  
-  // Read current state of packages
-  Read("package.json")
-  Read("CLAUDE.md")
-  
-  // Synchronize multiple files simultaneously
-  mcp__github__push_files {
-    branch: "sync/complete-integration",
-    files: [
-      { path: "packages/@monomind/cli/package.json", content: "[aligned package.json]" },
-      { path: "packages/@monomind/cli/CLAUDE.md", content: "[synchronized CLAUDE.md]" },
-      { path: ".claude/commands/github/github-modes.md", content: "[GitHub modes]" }
-    ],
-    message: "feat: Complete package synchronization with GitHub integration"
-  }
-  
-  // Run validation tests
-  Bash("npm install && npm test")
-  
-  // Track synchronization progress
-  TodoWrite { todos: [
-    { id: "sync-deps", content: "Synchronize package dependencies", status: "completed", priority: "high" },
-    { id: "sync-docs", content: "Align documentation", status: "completed", priority: "medium" },
-    { id: "sync-github", content: "Add GitHub command integration", status: "completed", priority: "high" },
-    { id: "sync-test", content: "Validate synchronization", status: "completed", priority: "medium" },
-    { id: "sync-pr", content: "Create integration PR", status: "pending", priority: "high" }
-  ]}
-  
-  // Store comprehensive sync state
-  mcp__monomind__memory_store {
-    key: "sync/complete/status",
-    value: {
-      timestamp: Date.now(),
-      version_alignment: "completed",
-      documentation_sync: "completed",
-      github_integration: "completed",
-      validation_status: "passed"
-    }
-  }
-```
-
-## Synchronization Strategies
-
-### 1. **Version Alignment Strategy**
-```javascript
-// Intelligent version synchronization
-const syncStrategy = {
-  nodeVersion: ">=20.0.0",  // Align to highest requirement
-  dependencies: {
-    "better-sqlite3": "^12.2.0",  // Use latest stable
-    "ws": "^8.14.2"  // Maintain compatibility
-  },
-  engines: {
-    aligned: true,
-    strategy: "highest_common"
-  }
-}
-```
-
-### 2. **Documentation Sync Pattern**
-```javascript
-// Keep documentation consistent across packages
-const docSyncPattern = {
-  sourceOfTruth: "CLAUDE.md",
-  targets: [
-    "packages/@monomind/cli/CLAUDE.md",
-    "packages/@monomind/hooks/CLAUDE.md"
-  ],
-  customSections: {
-    "@monomind/cli": "GitHub Commands Integration",
-    "@monoes/hooks": "MCP Tools Reference"
-  }
-}
-```
-
-### 3. **Integration Testing Matrix**
-```javascript
-// Comprehensive testing across synchronized packages
-const testMatrix = {
-  packages: ["@monomind/cli", "@monoes/hooks"],
-  tests: [
-    "unit_tests",
-    "integration_tests", 
-    "cross_package_tests",
-    "mcp_integration_tests",
-    "github_workflow_tests"
-  ],
-  validation: "parallel_execution"
-}
-```
-
-## Best Practices
-
-### 1. **Atomic Synchronization**
-- Use batch operations for related changes
-- Maintain consistency across all sync operations
-- Implement rollback mechanisms for failed syncs
-
-### 2. **Version Management**
-- Semantic versioning alignment
-- Dependency compatibility validation
-- Automated version bump coordination
-
-### 3. **Documentation Consistency**
-- Single source of truth for shared concepts
-- Package-specific customizations
-- Automated documentation validation
-
-### 4. **Testing Integration**
-- Cross-package test validation
-- Integration test automation
-- Performance regression detection
-
-## Monitoring and Metrics
-
-### Sync Quality Metrics:
-- Package version alignment percentage
-- Documentation consistency score
-- Integration test success rate
-- Synchronization completion time
-
-### Automated Reporting:
-- Weekly sync status reports
-- Dependency drift detection
-- Documentation divergence alerts
-- Integration health monitoring
-
-## Error Handling and Recovery
-
-### Automatic handling of:
-- Version conflict resolution
-- Merge conflict detection and resolution
-- Test failure recovery strategies
-- Documentation sync conflicts
-
-### Recovery procedures:
-- Automated rollback on critical failures
-- Incremental sync retry mechanisms
-- Manual intervention points for complex conflicts
-- State preservation across sync operations