Weyoun/chess
1
0
Fork 0
Code Issues 3 Pull Requests 1 Actions Packages Projects Releases Wiki Activity
chess/.claude/commands/github/github-swarm.md
Christoph Wagner 5ad0700b41 refactor: Consolidate repository structure - flatten from workspace pattern 
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>
2025-11-23 10:05:26 +01:00

2.4 KiB
Raw Blame History

github swarm

Create a specialized swarm for GitHub repository management.

Usage

npx claude-flow 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

npx claude-flow github swarm --repository owner/repo

Maintenance-focused swarm

npx claude-flow github swarm -r owner/repo -f maintenance --issue-labels

Development swarm with PR automation

npx claude-flow github swarm -r owner/repo -f development --auto-pr --code-review

Full-featured triage swarm

npx claude-flow 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:

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