pitroom-finishing
From the author
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.
Install
npx skills add ATASTECH/pitroom --skill pitroom-finishing -a claude-code
Installs to .claude/skills/pitroom-finishing/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- finishing-a-development-branchjnMetaCode/superpowers-zh当实现完成、所有测试通过、需要决定如何集成这份工作时使用Other★ 8.4K
- pitroom-crewATASTECH/pitroomUse 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.Testing★ 51
- pitroom-reviewATASTECH/pitroomUse 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.Engineering★ 51
- merge-protocolNoobyGains/godmodeUse when implementation on a branch is finished and reviewed and the work needs to land, be proposed as a pull request, be parked for later, or be thrown away.Engineering★ 115
- pitroom-verificationATASTECH/pitroomUse 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.Other★ 51
- branch-integrationthiientv/godmodeCloses a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.Productivity★ 99
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in