Fleet
All packs

Pull requests

Every fix or feature ends as a proven, reviewed draft pull request, and ship words take it to merged.

On by default

Add to your Fleet

How it works

  1. Your request
  2. Tests, then the fix
  3. Review by a second model
  4. Draft pull request

Workflows

  • Draft PR flow

    On with the packNeeds GitHub

    Every fix or feature ends as a proven, reviewed draft pull request that you mark ready yourself.

  • PR care

    On with the packNeeds GitHub

    When you ask, an agent watches a pull request, fixes CI, and answers review comments, and it can refresh a stale one.

  • Ship words

    On with the packNeeds GitHub

    Say "full send" or "stamp it", and the agent takes a pull request to merged and rolled out.

    Read before you turn it on

    The agent merges without asking again once you say the words.

  • PR owners

    On with the pack

    A thread that still owns an open pull request cannot settle or archive itself until it hands the pull request over, and a box with such a thread is not released.

What it costs

It needs GitHub, and setup signs you in. Each pull request spends extra usage on reviews. Expect at least one round, often two, and short final reads.

Know before you turn it on

Ship words merge without asking again. Say them only for work you would merge yourself.

Settings10 settings that your agent asks about
  • pull-requests.commentApprovalWhich comments should agents show you before they post them?Default: people
  • pull-requests.mergeCommandWhich command merges a pull request when the repo names no merge method? Leave it empty to merge as the rollout skill says.
  • pull-requests.freeReviewsHow many review rounds may run before the review arbiter decides whether another round is worth it?Default: 2
  • pull-requests.reviewCeilingAfter how many review rounds does review stop for good?Default: 6
  • pull-requests.criticalPathFilesWhich file lists the critical paths of each repository, as owner/name=path pairs separated by commas? A path is relative to your home folder. The judge fails a merge-risk Tier line that is not critical when the diff touches a path on the list.
  • pull-requests.reviewTimeoutMinutesHow many minutes may one review run before it counts as failed?Default: 20
  • pull-requests.panelSlotsHow many reviewers may run at once in a review panel?Default: 3
  • pull-requests.reviewFallbackWhat should fleet pr review tell an agent to do when no pack provides a review bot? {repo} and {pr} stand for the pull request.
  • pull-requests.stampFallbackWhat should fleet pr stamp tell an agent to do when no pack provides a review bot? {repo} and {pr} stand for the pull request.
  • pull-requests.approvalBotWhich bot or reviewer should approve a pull request when you say "stamp it"?

Add Pull requests to your Fleet

Paste this prompt into a T3 Code thread on a machine that runs Fleet.

Your install prompt

Add this Fleet pack to my setup with me: Pull requests.

Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself.

1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on.
2. Turn the packs on with one command:
   fleet packs --add pull-requests
3. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens.
4. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.
Open in T3 Code

Add more packs in one prompt