Agent skill · Code Review & Quality

ralph-wiggum-pm

Ralph Wiggum: Project Manager — Continuous ticket consumption, code review, and work generation loop. Picks up the next ticket, does the work, creates a PR, runs code review, logs completion, and creates follow-up tickets. Use when asked to start the loop, consume tickets, or grind through work.

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill ralph-wiggum-pm --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 16 KB
Bundled scripts: none
Allowed tools: -mcp__linear-server__list_issues-mcp__linear-server__get_issue-mcp__linear-server__save_issue-mcp__linear-server__save_comment-mcp__linear-server__list_comments-mcp__linear-server__list_issue_labels
Path: skills/agent/ralph-wiggum-pm/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Ralph Wiggum: Project Manager *"Me fail English? That's unpossible!"* — But you won't fail at grinding through tickets. You are a continuous work loop agent. You consume tickets from Linear, execute the work, push PRs, run code reviews, log what was done, and generate follow-up tickets for newly discovered work. Always chewing, always producing. ## Dependencies This skill invokes other skills during the loop. If a dependency is unavailable, the loop degrades gracefully rather than failing: | Skill | Used in | If unavailable | |-------|---------|----------------| | `/code-review` | Phase 3 (REVIEW) | Skip review, post a comment noting "code review unavailable — merged without review", proceed to QUALITY | | `/impeccable:critique` | Phase 4 (QUALITY Gate 2) | Skip Gate 2, run only Playwright tests, note in LOG | | `record-session.mjs` | Session Recording | Skip session recording if the script doesn't exist at `website/scripts/record-session.mjs` | Before the first cycle, verify dependencies are available and report any that are missing. The loop should never crash because a sub-skill isn't installed. ## Session Recording The loop automatically records its activity to `website/src/d

What's inside
Steps it walks through
  1. Dependencies
  2. Session Recording
  3. The Loop
  4. Phase 1: CONSUME (Pick Next Ticket)
  5. Phase 2: EXECUTE (Do the Work)
  6. Error Recovery
  7. Phase 3: REVIEW (Code Review Gate)
  8. Phase 4: QUALITY (UI Quality Gates)
  9. Phase 4.5: MERGE (Land the Code)
  10. Phase 5: LOG (Record Completion)
  11. Phase 6: GENERATE (Create Follow-up Work)
  12. Phase 7: RECORD (Log Session Data)
  13. Then Loop Back to CONSUME
  14. Loop Controls
Ships with 1 file
  • metadata.json
Commands it runs
cd website && node scripts/record-session.mjs start
cd website && node scripts/record-session.mjs cycle \
cd website && node scripts/record-session.mjs end
git branch --show-current  # Should NOT be "main"
gh pr view --json state     # Should be "OPEN"
git diff --name-only main..HEAD
cd website && pnpm exec playwright test 2>&1
More from claude-skill-registry
All skills →
About this skill
What does the ralph-wiggum-pm skill do?

Ralph Wiggum: Project Manager — Continuous ticket consumption, code review, and work generation loop. Picks up the next ticket, does the work, creates a PR, runs code review, logs completion, and creates follow-up tickets. Use when asked to start the loop, consume tickets, or grind through work.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill ralph-wiggum-pm --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going