Skip to content
Back to skills

Github Repo Architect

ASecurity

Repository structure optimization and multi-repo management with Monomind swarm coordination for scalable project architecture and development workflows.

  • 21 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 10, 2026
ai-agentsjavascriptjavabashnodetestinggitperformancedocumentation

Works with

  • claude code
  • cli
  • mcp

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned October 1, 2026

npx -y skills add monoes/monomind --skill github-repo-architect --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Github Repo Architect?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Github Repo Architect
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/monoes-github-repo-architect/badge)](https://www.skillsdirectory.com/skills/monoes-github-repo-architect)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: github-repo-architect
description: Repository structure optimization and multi-repo management with Monomind swarm coordination for scalable project architecture and development workflows.
type: flow
---

# 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
// Spawn architecture analysis agents
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__task_create {
  description: "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]:
  // Spawn comprehensive architecture agents
  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_pattern-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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…