pitroom

In the author's own words, from each skill's SKILL.md.

• pitroom-brainstorming

  Use when you or the user want a feature, component or behaviour change designed before it is built - explores intent, requirements and design with the user and gets approval before implementation.

  skills/pitroom-brainstorming/SKILL.md on GitHub (opens in a new tab)

• pitroom-crew

  Use when facing two or more independent tasks - questions about different areas, unrelated bugs or failing test files, the same mechanical change in separate modules - to run Pitroom workers in parallel, watch them live and merge their results.

  skills/pitroom-crew/SKILL.md on GitHub (opens in a new tab)

• pitroom-debugging

  Use when a bug, test failure or unexpected behaviour has no obvious cause and you want a root-cause process before proposing fixes - with Pitroom workers gathering the evidence.

  skills/pitroom-debugging/SKILL.md on GitHub (opens in a new tab)

• pitroom-driven-development

  Use when executing a written implementation plan - each task goes to a Pitroom worker in an isolated copy, a worker on another model reviews it, and you rule, apply and commit between tasks.

  skills/pitroom-driven-development/SKILL.md on GitHub (opens in a new tab)

• pitroom-finishing

  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - verifies, presents merge / pull request / keep options, and executes the one your human partner chooses.

  skills/pitroom-finishing/SKILL.md on GitHub (opens in a new tab)

• pitroom-implement

  Use for well-defined code changes a cheaper worker can make - small bug fixes, simple features, mechanical refactors, renames, writing tests, fixing lint or type errors, docs - where you can state the goal and check the result with a diff or tests.

  skills/pitroom-implement/SKILL.md on GitHub (opens in a new tab)

• pitroom-receiving-review

  Use when receiving code review feedback - from a Pitroom reviewer, a colleague or a pull request - before implementing suggestions, especially if feedback seems unclear or technically questionable; requires technical rigor and verification, not performative agreement or blind implementation.

  skills/pitroom-receiving-review/SKILL.md on GitHub (opens in a new tab)

• pitroom-research

  Use when you need to find, map or explain code - where something is defined or called, how a flow works end to end, which files a change would touch, what a large module does - and the answer is much smaller than what must be read. Runs a read-only Pitroom worker and returns its answer with verified file references.

  skills/pitroom-research/SKILL.md on GitHub (opens in a new tab)

• pitroom-review

  Use when completing a task, implementing a major feature, before merging, or whenever you want a second opinion on a diff, branch or pull request - a read-only Pitroom worker on another model reviews it against its requirements.

  skills/pitroom-review/SKILL.md on GitHub (opens in a new tab)

• pitroom-tdd

  Use when you want to drive a feature or bugfix test-first - red, green, refactor, for you and for the workers you brief.

  skills/pitroom-tdd/SKILL.md on GitHub (opens in a new tab)

• pitroom-verification

  Use when you want evidence before claiming work is complete, fixed or passing, or before committing or opening a PR - run the checks and read their output first, including for claims a worker made.

  skills/pitroom-verification/SKILL.md on GitHub (opens in a new tab)

• pitroom-worktrees

  Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan - sets up an isolated branch for your own work (workers get isolated copies from Pitroom itself).

  skills/pitroom-worktrees/SKILL.md on GitHub (opens in a new tab)

• pitroom-writing-plans

  Use when you have a spec or requirements for a multi-step task, before touching code - writes a task-by-task implementation plan that Pitroom workers can execute.

  skills/pitroom-writing-plans/SKILL.md on GitHub (opens in a new tab)

• using-pitroom

  Use when you want cheap Pitroom workers or its workflow skills for a task, or when the user asks for Pitroom - a menu of the pitroom-* skills (brainstorm, plan, worker-driven development, review, debugging, TDD, verification, finishing), when each pays off, and how to run workers. Optional; skip it for work you would rather do yourself.

  skills/using-pitroom/SKILL.md on GitHub (opens in a new tab)

No skill matches that filter.

Similar skills

• khazix-skillsby KKKKhazix 数字生命卡兹克开源的 AI Skills 合集 | Agent Skills: leader（帮你定义目标）, neat-freak 洁癖, hv-analysis, khazix-writer & more — Claude Code, Codex & 40+ agents 21.4k stars · 6 skills
• agent-skills-platformby FrancyJGLisboa Build tested agent skills and govern their lifecycle through a user-defined marketplace: evidence, discovery, updates, rollback, quarantine… 2.4k stars · 6 skills
• ECCby affaan-m The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Cod… 280k stars · 30 skills
• reaby morluto Reverse engineer anything with agents, from app behavior down to native binaries. 270k stars · 1 skill
• taste-skillby Leonxlnx Agent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages 97.3k stars · 13 skills
• archifyby tt-a1i Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more. 84.1k stars · 2 skills