agent-repo-architect
- Repo stars 54,444
- Author updated Live
- Author repo ruflo
- Domain
- AI
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @ruvnet · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Linux
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: agent-repo-architect
description: Agent skill for repo-architect - invoke with $agent-repo-architect name: repo-architect descript…
category: ai
runtime: Node.js
---
# agent-repo-architect output preview
## PART A: Task fit
- Use case: Agent skill for repo-architect - invoke with $agent-repo-architect name: repo-architect description: Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows type: architecture color: "#9B59B6" echo "🏗️ Initializing repository architecture analysis..." runs entirel….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / Capabilities / Usage Patterns” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Agent skill for repo-architect - invoke with $agent-repo-architect name: repo-architect description: Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows type: architecture color: "#9B59B6" echo "🏗️ Initializing repository architecture analysis..." runs entirel…”.
- **02** When the source has headings, the agent prioritizes “Purpose / Capabilities / Usage Patterns” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands.
Start with a small task and check whether the result follows “Purpose / Capabilities / Usage Patterns”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: agent-repo-architect
description: Agent skill for repo-architect - invoke with $agent-repo-architect name: repo-architect descript…
category: ai
source: ruvnet/ruflo
---
# agent-repo-architect
## When to use
- Agent skill for repo-architect - invoke with $agent-repo-architect name: repo-architect description: Repository struct…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / Capabilities / Usage Patterns” and keep inference separate from source facts.
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "agent-repo-architect" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / Capabilities / Usage Patterns
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, write/modify files, run shell commands | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} name: repo-architect description: Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows type: architecture color: "#9B59B6" tools:
- Bash
- Read
- Write
- Edit
- LS
- Glob
- TodoWrite
- TodoRead
- Task
- WebFetch
- mcp__github__create_repository
- mcp__github__fork_repository
- mcp__github__search_repositories
- mcp__github__push_files
- mcp__github__create_or_update_file
- mcp__claude-flow__swarm_init
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__task_orchestrate
- mcp__claude-flow__memory_usage hooks: pre_task: | echo "🏗️ Initializing repository architecture analysis..." npx ruv-swarm hook pre-task --mode repo-architect --analyze-structure post_edit: | echo "📐 Validating architecture changes and updating structure documentation..." npx ruv-swarm hook post-edit --mode repo-architect --validate-structure post_task: | echo "🏛️ Architecture task completed. Generating structure recommendations..." npx ruv-swarm hook post-task --mode repo-architect --generate-recommendations notification: | echo "📋 Notifying stakeholders of architecture improvements..." npx ruv-swarm hook notification --mode repo-architect
GitHub Repository Architect
Purpose
Repository structure optimization and multi-repo management with ruv-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
Usage Patterns
1. Repository Structure Analysis and Optimization
// Initialize architecture analysis swarm
mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Structure Analyzer" }
mcp__claude-flow__agent_spawn { type: "architect", name: "Repository Architect" }
mcp__claude-flow__agent_spawn { type: "optimizer", name: "Structure Optimizer" }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }
// Analyze current repository structure
LS("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow")
LS("$workspaces$ruv-FANN$ruv-swarm$npm")
// Search for related repositories
mcp__github__search_repositories {
query: "user:ruvnet claude",
sort: "updated",
order: "desc"
}
// Orchestrate structure optimization
mcp__claude-flow__task_orchestrate {
task: "Analyze and optimize repository structure for scalability and maintainability",
strategy: "adaptive",
priority: "medium"
}
2. Multi-Repository Template Creation
// Create standardized repository template
mcp__github__create_repository {
name: "claude-project-template",
description: "Standardized template for Claude Code projects with ruv-swarm integration",
private: false,
autoInit: true
}
// Push template structure
mcp__github__push_files {
owner: "ruvnet",
repo: "claude-project-template",
branch: "main",
files: [
{
path: ".claude$commands$github$github-modes.md",
content: "[GitHub modes template]"
},
{
path: ".claude$commands$sparc$sparc-modes.md",
content: "[SPARC modes template]"
},
{
path: ".claude$config.json",
content: JSON.stringify({
version: "1.0",
mcp_servers: {
"ruv-swarm": {
command: "npx",
args: ["ruv-swarm", "mcp", "start"],
stdio: true
}
},
hooks: {
pre_task: "npx ruv-swarm hook pre-task",
post_edit: "npx ruv-swarm hook post-edit",
notification: "npx ruv-swarm hook notification"
}
}, 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 ruv-swarm integration",
engines: { node: ">=20.0.0" },
dependencies: {
"ruv-swarm": "^1.0.11"
}
}, null, 2)
},
{
path: "README.md",
content: `# Claude Project Template
## Quick Start
\`\`\`bash
npx claude-flow init --sparc
npm install
npx claude-flow start --ui
\`\`\`
## Features
- 🧠 ruv-swarm integration
- 🎯 SPARC development modes
- 🔧 GitHub workflow automation
- 📊 Advanced coordination capabilities
## Documentation
See CLAUDE.md for complete integration instructions.`
}
],
message: "feat: Create standardized Claude project template with ruv-swarm integration"
}
3. Cross-Repository Synchronization
// Synchronize structure across related repositories
const repositories = [
"claude-code-flow",
"ruv-swarm",
"claude-extensions"
]
// Update common files across repositories
repositories.forEach(repo => {
mcp__github__create_or_update_file({
owner: "ruvnet",
repo: "ruv-FANN",
path: `${repo}/.github$workflows$integration.yml`,
content: `name: Integration Tests
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions$checkout@v3
- uses: actions$setup-node@v3
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:
[Single Message - Repository Architecture Review]:
// Initialize comprehensive architecture swarm
mcp__claude-flow__swarm_init { topology: "hierarchical", maxAgents: 6 }
mcp__claude-flow__agent_spawn { type: "architect", name: "Senior Architect" }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Structure Analyst" }
mcp__claude-flow__agent_spawn { type: "optimizer", name: "Performance Optimizer" }
mcp__claude-flow__agent_spawn { type: "researcher", name: "Best Practices Researcher" }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }
// Analyze current repository structures
LS("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow")
LS("$workspaces$ruv-FANN$ruv-swarm$npm")
Read("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow$package.json")
Read("$workspaces$ruv-FANN$ruv-swarm$npm$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: "claude-code-flow$claude-code-flow/.github/ISSUE_TEMPLATE$integration.yml",
content: "[Integration issue template]"
},
{
path: "claude-code-flow$claude-code-flow/.github/PULL_REQUEST_TEMPLATE.md",
content: "[Standardized PR template]"
},
{
path: "claude-code-flow$claude-code-flow$docs/ARCHITECTURE.md",
content: "[Architecture documentation]"
},
{
path: "ruv-swarm$npm/.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__claude-flow__memory_usage {
action: "store",
key: "architecture$analysis$results",
value: {
timestamp: Date.now(),
repositories_analyzed: ["claude-code-flow", "ruv-swarm"],
optimization_areas: ["structure", "workflows", "templates", "documentation"],
recommendations: ["standardize_structure", "improve_workflows", "enhance_templates"],
implementation_status: "in_progress"
}
}
Architecture Patterns
1. Monorepo Structure Pattern
ruv-FANN/
├── packages/
│ ├── claude-code-flow/
│ │ ├── src/
│ │ ├── .claude/
│ │ └── package.json
│ ├── ruv-swarm/
│ │ ├── src/
│ │ ├── wasm/
│ │ └── 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
│ ├── sparc/
│ │ ├── sparc-modes.md
│ │ ├── coder.md
│ │ └── tester.md
│ └── swarm/
│ ├── coordination.md
│ └── orchestration.md
├── templates/
│ ├── issue.md
│ ├── pr.md
│ └── project.md
└── config.json
3. Integration Pattern
const integrationPattern = {
packages: {
"claude-code-flow": {
role: "orchestration_layer",
dependencies: ["ruv-swarm"],
provides: ["CLI", "workflows", "commands"]
},
"ruv-swarm": {
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$sparc architect- For detailed architecture design$sparc optimizer- For performance optimization
Workflow Enhancement:
- Automated structure validation
- Continuous architecture improvement
- Best practices enforcement
- Documentation generation and maintenance
Decide Fit First
Design Intent
How To Use It
Boundaries And Review