Index of every page on this site: llms.txt
All skills
vercel avatar

/pr-lifecycle

@86694bd
by vercelvercel/board147 stars
13
Run it yourself

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.

  • 1 file
  • 2.8 KB
  • Updated 4 days ago
  • GitHub
Use this Skill: https://skilld.dev/gh/vercel/board/pr-lifecycle

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈48 tokens for metadata: the name and description. ≈671 when used: this file.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈192 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 86694bd. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 12 hours ago.

Activeupdated 4 days ago

README badge

README badge for vercel/board/pr-lifecycle