ratchet-next

Advances or reworks GitHub pull requests after merge or review events.

2|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/praveenvijayan/Ratchet --skill ratchet-next-praveenvijayan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratchet-next
Source: https://github.com/praveenvijayan/Ratchet/tree/main/plugin/skills/ratchet-next
Command: npx skills add https://github.com/praveenvijayan/Ratchet --skill ratchet-next-praveenvijayan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a human reviews or merges a pull request, coding agents often stall or take the wrong next step. This Skill decides what happened to the work in flight and executes the correct follow-up locally, without CI or API keys. ## Core Features & Use Cases - Advance on merge: Syncs main with a fast-forward pull, removes the merged issue's worktree, claims the next ready issue, and starts building it in a new worktree. - Rework on rejection: Handles Request Changes reviews, closed-with-comment PRs, and direct chat feedback by fixing issues on the same branch and updating the existing PR. - Ownership verification: Checks the .ratchet-owner marker before resuming any in-progress work, preventing agents from touching foreign branches or PRs. - Use Case: After your PR gets a Request Changes review, invoke this Skill to gather all review comments, apply focused fixes in the issue worktree, re-run the GATES.md checks, push, and reply to each comment with the resolving commit SHA. ## Quick Start Ask the agent to run ratchet-next after the latest PR review to either start the next ready issue or rework the current branch based on the feedback.

Frequently Asked Questions about ratchet-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I continue work after a pull request is merged?

Run the advance path: fetch and fast-forward main, remove the merged issue's worktree, then claim the top ready unblocked issue and attach it as a new worktree. Build to the acceptance criteria, run the GATES.md gates, and open a PR with Closes #<N>.

How do I handle a Request Changes review on a GitHub PR?

Gather the review summary and line comments with gh pr view and the pulls comments API, apply focused fix commits in the issue's worktree, re-run the gates, and push to the same branch. Reply to each review comment with the commit SHA that resolves it, then set the issue back to in-review.

Can an agent resume work started by another agent?

Only with proof of ownership: the conversation claimed the issue, or a human explicitly hands it over via chat feedback or a watcher event. The .ratchet-owner marker in the worktree is checked against your OWNER_ID; foreign in-progress work is never touched.

What happens when no issues are in the ready state?

The Skill does not stop at reporting drained. It diagnoses the cause by counting issue states, finding draft issues missing acceptance criteria, tracing blocked chains to their root, and checking for open planning PRs, then reports the single next unblocking action.

Does this Skill merge or approve pull requests?

No, the agent never merges or approves. Non-high-risk PRs are merged by the auto-merge workflow once checks are green and the latest review verdict is APPROVED; risk:high PRs additionally wait for a human approval and a 15-minute hold.