Skills / development-and-testing
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
AI & AutomationSecurityauditautomationcleanupcode-reviewdevtoolsgitgithubrepository
OpenClaw GitHub Repo Commander
Overview
A structured 7-stage super workflow for comprehensive GitHub repository management. This skill automates repository auditing, cleanup, competitor benchmarking, and optimization — turning a messy repo into a clean, well-documented, production-ready project.
When to Use This Skill
- Use when you need to audit a repository for secrets, junk files, or low-quality content
- Use when the user says "clean up my repo", "optimize my GitHub project", or "audit this library"
- Use when reviewing or creating pull requests with structured analysis
- Use when comparing your project against competitors on GitHub
- Use when running
/super-workflowor/openclaw-github-repo-commanderon a repo URL
How It Works
Stage 1: Intake
Clone the target repository, define success criteria, and establish baseline metrics.
Stage 2: Execution
Run scripts/repo-audit.sh <repo-path> from this skill directory — automated read-only checks for:
- Hardcoded secrets (
ghp_,sk-,AKIA, etc.) - Tracked
node_modules/or build artifacts - Empty directories
- Large files (>1MB)
- Missing
.gitignorecoverage - Broken internal README links
Stage 3: Reflection
Deep manual review beyond automation: content quality, documentation consistency, structural issues, version mismatches.
Stage 4: Competitor Analysis
Search GitHub for similar re
Subscribers only
The full skill, its 2 bundled files and every download is included with every paid Complete AI plan.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | safe ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md, scripts/repo-audit.sh |
| Added | 2026-03-18 |
Related skills
bug-hunter
Systematically finds and fixes bugs using proven debugging techniques. Traces from symptoms to root cause, implements fixes, and prevents regression.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
debugging-strategies
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
test-fixing
Systematically identify and fix all failing tests using smart grouping strategies. Use when explicitly asks to fix tests ("fix these tests", "make tests pass"), reports test failures ("tests are failing", "test suite is broken"), or completes implementation and wants tests passing.