openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
Best for Repository maintainersWorks with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·7-stage structured workflow for repository management
- ·Automated audit for hardcoded secrets and junk files
- ·Checks for missing .gitignore coverage and large files
- ·Supports competitor benchmarking and analysis
- ·Triggers via specific slash commands or user requests
Use Cases
- →Auditing a repository for exposed secrets and low-quality content
- →Cleaning up a messy repository to make it production-ready
- →Reviewing or creating pull requests with structured analysis
- →Comparing your project against competitor repositories on GitHub
Best for
- ✓Repository maintainers
- ✓Teams conducting security audits
- ✓Developers optimizing open-source projects
Not ideal for
- !Use this skill only when the task clearly matches the scope described above.
- !Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- !Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
name
openclaw-github-repo-commander
description
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis
category:development-and-testing
risk:safe
source:community
date_added:2026-03-18
author:wd041216-bit
tags:["github","git","repository","audit","cleanup","workflow","devtools","automation","code-review","security"]
tools:["claude","cursor"]
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 — automated 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
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill openclaw-github-repo-commanderSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.