prepare-todero-pr

Prepares a Todero branch into a reviewed pull request with commits, rebase, and Greptile review loops.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill prepare-todero-pr-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-todero-pr
Source: https://github.com/nabitllc/todero/tree/main/.agents/skills/prepare-todero-pr
Command: npx skills add https://github.com/nabitllc/todero --skill prepare-todero-pr-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning finished branch work into a clean, reviewed pull request involves many error-prone steps: committing everything, rebasing on master, respecting repo guardrails, opening the PR, and iterating on automated review feedback. This Skill standardizes that entire procedure for the Todero repository so no work is lost and every PR meets the project's review bar. ## Core Features & Use Cases - Worktree-safe PR preparation: Verifies you are on a dedicated branch in a git worktree, commits all changes with the required Co-Authored-By trailer, and rebases cleanly on top of the target master. - Guardrail enforcement: Blocks committing pnpm-lock.yaml, unexpected workflow changes, and design screenshots; enforces incremental idempotent migrations and a 100-changed-files PR limit. - Automated review loops: Runs Greptile review until it reaches 5/5 with zero unresolved comments, then runs verification/CI checks, and reports PR URLs, worktree path, and check status back to the driving task. - Use Case: An agent finishes a feature branch for the Todero repo and needs it merged-ready: this Skill commits the work, rebases on master, opens the PR with gh per CONTRIBUTING.md, and iterates on Greptile feedback until the PR is green. ## Quick Start Prepare my current Todero branch as a pull request against master, following the full commit, rebase, guardrail, and Greptile review procedure.

Frequently Asked Questions about prepare-todero-pr

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

FAQPage Schema
How do I prepare a branch for a pull request in the Todero repo?

Work in a git worktree on a dedicated branch, commit all changes with the Co-Authored-By: Todero trailer, rebase onto the target master, then push and open the PR with gh following CONTRIBUTING.md. Finally run the Greptile review loop until it scores 5/5.

How do I run Greptile review until a PR passes?

Trigger the Greptile review on the opened PR, address each of its comments, push the fixes, and repeat for up to 20 turns. Do not stop until Greptile reports 5/5 with zero unresolved comments and all CI checks pass.

Why should I never commit pnpm-lock.yaml in a Todero PR?

The Todero repository has automated actions that manage pnpm-lock.yaml, so committing it manually causes conflicts. If it is already in a commit, rewrite or drop that change before pushing the branch.

What happens if my PR changes more than 100 files?

Greptile has a file limit, so any PR exceeding 100 changed files must be split into two separate PRs. Run the full preparation procedure independently for each resulting PR.

Can I merge my own pull request after Greptile passes?

No. The procedure explicitly forbids merging the PR yourself under any circumstances. Your job ends at reporting the PR URL, Greptile score, worktree path, and check status back to the driving task.