Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    PR Ready: Checks, Stacked PRs, and Honest Descriptions

    1

    When asked to tidy up history they stall, because `git rebase -i` and `git add -p` need a human at the keyboard.

    $12

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    PR Ready: Checks, Stacked PRs, and Honest Descriptions

    PR Ready: Checks, Stacked PRs, and Honest Descriptions

    Example session with this skill installed

    This branch got big. Make it PR-ready and open the PRs. The repo uses conventional commits and DCO.

    • Read your context and instructions
    • Compiled the pr ready

    Example session (illustrative).

    Repo rules found

    • Gate: make ci (mirrors ci.yml)
    • Commits: commitlint with @commitlint/config-conventional; scopes api, web, db
    • DCO: dco.yml checks every commit
    • PR title must be a conventional header (the repo squash-merges)
    • CONTRIBUTING requires disclosing agent authorship

    Checks on the current HEAD

    • make ci: exit 0, 218 passed, 0 failed, lint 0 warnings
    • git diff --check origin/main...HEAD: clean

    Self-review

    • removed console.log(payload) in web/src/checkout.ts:88
    • removed it.only in api/test/orders.test.ts:41
    • reverted whitespace-only changes in 3 files outside the task
    • one new TODO is now linked to #412

    Size: 1,140 changed lines across 23 files. This mixes a rename, a schema change and the feature, so I proposed a 3-PR stack, which you approved:

    #TitleLinesBase
    1refactor(api): rename OrderTotal to OrderAmount310main
    2feat(db): add currency column to orders190#1
    3feat(web): show order currency at checkout640#2

    After splitting

    • backup branch backup/feat-currency created
    • each branch built with git restore --source=feat-currency --staged --worktree -- <paths> and committed with -s
    • make ci passed on all three branches (218, 221 and 229 tests)
    • git diff --quiet feat-currency feat-currency-3: identical, so nothing was lost

    PR bodies are drafted. Each one has What/Why, How tested with the commands above, Risk and rollback (PR 2 includes a reversible migration with its down step), a screenshot slot for PR 3, "Part N of 3", and the agent-disclosure line, with a placeholder for you to add the human author of record.

    Ready to run, waiting for your OK: git push -u origin for each of the three branches, then three gh pr create --draft calls with --base set to the previous branch. Shall I go ahead?

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem. Coding agents produce PRs that are too big, mix refactors with behavior changes, leave console.log and .only behind, and claim "all tests pass" without having run anything. When asked to tidy up history they stall, because git rebase -i and git add -p need a human at the keyboard. Reviewers end up doing the cleanup.

    What the agent does.

    • Learns your repo's rules. It reads AGENTS.md, CONTRIBUTING, PR templates, commitlint config and CI workflows to find the gate command, the commit format, whether DCO sign-off is required, PR title rules and agent-disclosure requirements.
    • Runs the real checks first. Results are recorded as exact commands with their exit codes and summary lines. Anything it couldn't run is listed as "not run", with the reason.
    • Self-reviews the diff. It checks for debug leftovers, focused tests, new TODOs, secrets, unrelated formatting churn, stray lockfile or build changes, and missing tests.
    • Splits oversized branches into an ordered stack. The order is prep, then internals, then behavior, then cleanup. It uses only non-interactive git:
      • git restore --source=<branch> --staged --worktree for stacked branches
      • git reset --soft to regroup commits on one branch
      • git apply --cached --unidiff-zero to stage individual hunks
      • cherry-pick to move existing commits
    • Proves nothing was lost. After splitting, it confirms the final tree is identical to the original.
    • Fixes commit messages and sign-off without interactive rebase: --amend -s for the last commit, rebase --signoff for the whole branch, and --force-with-lease only if you approve a push.
    • Drafts the PR description: what, why, how it was tested (with real commands and results), risk and rollback, screenshots for UI changes, and "Part N of M" links for stacks.
    • Waits for your go-ahead. It asks before rewriting history, pushing or running gh pr create.

    Who it's for. Developers who hand agent-written work to human reviewers, maintainers of repos with strict PR gates (Conventional Commits, DCO, size limits), and teams that want agent PRs to arrive ready to review.

    Requirements. An agent with shell access and git. The gh CLI is optional and only needed to open PRs. Works with any language. AgentHarness is not required.

    Requires git and gh CLI. Cannot rotate secrets if discovered. Relies on local environment to execute project test suites. Skip splitting if changes are deeply intertwined in single files.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 17 days ago

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Listed17 days ago

    What's inside

    Frequently Asked Questions

    It builds new branches from the base and brings files over with `git restore --source=<branch> --staged --worktree`. It can also regroup commits after `git reset --soft`, or stage individual hunks by applying a trimmed patch with `git apply --cached --unidiff-zero`. Then it checks that the final tree is identical to the original.

    No. It stops and asks before rewriting history, before pushing, and before `gh pr create`. It also always creates a backup branch before rewriting history.

    The "How tested" section lists the exact commands it ran in that session, with their exit codes and summary lines. Anything it could not run is listed as not run, with the reason. It never writes "tests pass" without having run them.

    Only when your repo requires them, which it works out from CONTRIBUTING, CI workflows or commit history. Sign-off always uses your configured git identity. For disclosure it names the agent and leaves the human author of record for you to fill in.

    You don't need AgentHarness. Everything except opening the PR is plain git, so it works with any host. Opening PRs uses the GitHub `gh` CLI; on other hosts you get the branches and descriptions ready to paste.

    New in Code Quality & Review