github-repo-health-wasp-drone — Claude Code subagent
github-repo-health-wasp-drone audits GitHub repository hygiene across eight structural areas. Helps teams find gaps in branch protection, CI configurations, and metadata without modifying code.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install wasp-nest-core@wasp-nestWhat github-repo-health-wasp-drone does
This subagent inspects GitHub repository structure across eight distinct dimensions: rulesets and branch protection, adherence to Conventional Commits, CODEOWNERS coverage, CI workflow density, documentation presence, .gitignore completeness, pull request and issue templates, and core project settings. Findings are scored and sorted by impact divided by effort.
Operation is strictly read-only. The drone never modifies configuration files, branch guards, or repository options. Depending on the environment, it uses local clone data, GitHub REST API tokens, or the gh command-line tool. Without API credentials or a logged-in CLI session on private projects, remote settings checks produce coverage gaps.
Specialized tasks are routed elsewhere. Complex CI pipeline reorganizations pass to devops-wasp-drone, leaked credentials and vulnerabilities route to security-wasp-drone, and structural rewrite work for documentation goes to readme-writing-wasp-drone.
What it helps with
- audit GitHub branch rulesets and merge settings
- evaluate commit histories for Conventional Commits adherence
- detect missing file patterns in CODEOWNERS and .gitignore
- generate prioritized hygiene checklists based on effort and impact
Example prompts for the agent
- audit this repo
- check branch protection and repository settings
- are our CI checks configured correctly
How to install github-repo-health-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install wasp-nest-core@wasp-nest2Manually: put the files in place
.claude/agents/github-repo-health-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/github-repo-health-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/github-repo-health-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about github-repo-health-wasp-drone
How to install github-repo-health-wasp-drone in Claude Code?
Add the marketplace source with /plugin marketplace add legioncodeinc/vibe-coding-tools, then run /plugin install wasp-nest-core@wasp-nest inside Claude Code.
What does github-repo-health-wasp-drone do?
It reviews repository metadata across eight dimensions, scores each from 0 to 10, and writes a diagnostic report prioritizing quick wins.
Will this subagent apply branch rules or edit repository files?
No, it functions strictly in read-only mode to keep evidence intact. It delivers concrete file paths and GitHub Settings URLs for your team to adjust manually.