---
name: pr-lifecycle
description: "See a pull request you opened through to merged or closed, with check-ins you schedule. Use right after gh pr create, and on every check-in that wakes you about one of your PRs."
title: pr-lifecycle
canonical_url: https://skilld.dev/gh/vercel/board/pr-lifecycle
last_updated: 2026-11-19T06:15:42.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install vercel/board/pr-lifecycle`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/pr-lifecycle`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/vercel/board/pr-lifecycle) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/pr-lifecycle`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/pr-lifecycle --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/pr-lifecycle --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# See your PR through

A PR you open is yours until it's merged or closed. Nothing GitHub does on it reaches you: you
only wake when a board message arrives. So you check on it yourself, with messages you schedule in
the thread you built it for. Each one wakes you when it's posted.

## Right after `gh pr create`

Schedule its check-ins, each with `--no-sync` so they stay out of Slack. Every one is a whole
turn of yours, and most find nothing, so they thin out as the PR ages:

- While its checks run:
  `vb schedule <id> "Check on <owner/repo>#<N>" --every 10m --times 6 --no-sync`
- Its first day:
  `vb schedule <id> "Check on <owner/repo>#<N>" --in 2h --every 4h --times 6 --no-sync`
- The week after:
  `vb schedule <id> "Check on <owner/repo>#<N>" --in 2d --every 1d --times 6 --no-sync`

A reply in the thread still reaches you at once, so nobody waits on a check-in to get your
attention. The check-ins skill has the rest: one set per open thing, and what to do when one
wakes you.

## On each check-in

Start on GitHub, not the board: the board doesn't show what changed on the PR.

```bash
gh pr view <N> --repo <owner/repo> --json state,reviewDecision,reviews,comments,statusCheckRollup
gh api repos/<owner/repo>/pulls/<N>/comments   # inline review comments
```

Then move it forward:

- **Its checks have finished:** cancel what's left of the first set.
- **A failing check:** read why. If your change broke it, fix it and push. If it's flaky or
  unrelated, re-run it once; if it fails the same way again, say which check and why in the
  thread instead of re-running it.
- **Review comments:** address each one, with a fix pushed or a reply on GitHub where you
  disagree.
- **Waiting on a review for more than a day:** ask once in the thread, mentioning whoever should
  review it. Don't ask again.
- **Approved, green, and nothing left open:** merge it if the repo's rules let you and the person
  who asked wants it merged. Otherwise say it's ready, and who can merge it.
- **No longer wanted, replaced by another PR, or stuck on a decision nobody's making:** say so,
  and close it once someone agrees.
- **Merged or closed:** say so in one line, and cancel its check-ins: `vb schedules <id>`, then
  `vb schedule cancel <schedule>` for each.
  When that settles what the thread asked for, mark the thread resolved: ✅ on its root.
- **The last check-in, and it's still open:** say once where it stands and who it's waiting on,
  and ask whether to keep it. Schedule more only if someone wants it kept. It's the last when
  `vb schedules <id>` shows none pending for the PR: the first two sets end long before.

A check-in that finds nothing new posts nothing.
