Automate GitHub Repo Audits and Optimization

This skill runs a structured 7-stage super workflow for comprehensive GitHub repository management: auditing, cleanup, competitor benchmarking, and optimization, turning a messy repo into a clean, well-documented, production-ready project. The stages are: Intake (clone the repo, define success criteria and baseline metrics), Execution (run the bundled scripts/repo-audit.sh for automated read-only checks), Reflection (manual review of content quality, documentation consistency, and structural issues), Competitor Analysis (search GitHub for similar repos and compare documentation, features, and adoption), Synthesis (consolidate findings into a P0/P1/P2 prioritized action plan), Iteration (execute the plan - delete low-value files, fix security issues, upgrade docs, add CI, update changelogs), and Validation (re-run the audit script targeting 7/7 PASS, verify changes, push, and deliver a full report).

Use it when you need to audit a repository for secrets, junk files, or low-quality content; when a user asks to "clean up my repo", "optimize my GitHub project", or "audit this library"; when reviewing or creating pull requests with structured analysis; or when comparing your project against competitors on GitHub.

Don't skip Stage 4 (competitor analysis) - it's called out specifically for revealing blind spots the internal audit misses. Don't commit node_modules/ or .env files as a shortcut instead of fixing the underlying .gitignore gaps the audit finds. Treat its output as a starting action plan, not a substitute for environment-specific validation or expert review - use it only when the task clearly matches this audit/cleanup/benchmarking scope, and stop to ask for clarification if required inputs, permissions, or success criteria are missing.

Input: a GitHub repo URL or an in-repo cleanup request. Output: a detailed before/after audit report and a prioritized (P0/P1/P2) action plan.

/openclaw-github-repo-commander https://github.com/owner/my-repo

Uses the gh CLI with the user's existing authentication (no credentials stored by the skill) and a bundled read-only repo-audit.sh script that scans for hardcoded secret patterns (ghp_, sk-, AKIA), tracked build artifacts, empty directories, large files, missing .gitignore coverage, and broken README links - excluding .github/workflows/ to avoid false positives. The audit script never deletes, rewrites, stages, commits, or pushes files on its own; all file changes in Stage 6 require explicit user confirmation.

Maintainers and developers who want a repeatable, structured process to audit, clean up, and benchmark a GitHub repository against similar projects before a release or public launch.