Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From gods
Discover the smallest powerful God Team for a review task or skill markdown, then use that team to guide a strict code-quality review.
npx claudepluginhub ancplua/earlybirdaiHow this skill is triggered — by the user, by Claude, or both
Slash command
/gods:reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this command for dynamic review-team discovery. `$ARGUMENTS` may be a skill path, markdown file, or free-form review
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Use this command for dynamic review-team discovery. $ARGUMENTS may be a skill path, markdown file, or free-form review
task.
Run the local discovery pipeline first:
python3 main.py --skill "$ARGUMENTS"
Then read results/god_team.json and use the selected team as workflow forces for the review. Do not treat the gods as
static subagents. If the selected team looks redundant, rerun with a clearer skill/task input before reviewing.
Review output should lead with blocking structural risks, then important maintainability risks, then the selected God Team summary. Keep the review focused on structural simplification, code-judo deletion, spaghetti growth, file-size/type/canonical-layer boundaries, orchestration atomicity, unnecessary abstraction rejection, evidence, and the approval bar. Do not substitute generic linting or style nits for the thermo-nuclear review intent.