contributor-setup
/contributor-setup
Bring a branch that predates next's agent rules up to date once, then fix the bodies of your open PRs into next. Use when the PR body check fails or when an agent opened a PR into next by hand.
Assessment and security
- Files in this package
- 2
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/doctor.mjs
What it does and when to use it
Bring a branch that predates next's agent rules up to date once, then fix the bodies of your open PRs into next. Use when the PR body check fails or when an agent opened a PR into next by hand.
Original author description
Bring a branch that predates next's agent rules up to date once, then fix the bodies of your open PRs into next. Use when the PR body check fails or when an agent opened a PR into next by hand.
How it works
SKILL.md has no level-two headings · 12 lines, 359 words
SKILL.md preview
---
description: Bring a branch that predates next's agent rules up to date once, then fix the bodies of your open PRs into next. Use when the PR body check fails or when an agent opened a PR into next by hand.
name: contributor-setup
metadata:
skiller:
source: .agents/rules/contributor-setup.mdc
---
# Contributor setup
A PR into `next` gets its body from `node .agents/pstack/land.mjs`. An agent that writes the body itself runs on a branch older than `next`'s agent rules. This skill brings the branch up to date once and fixes the bodies that already failed. After that, each session's start checks the agent's plugins against the checkout's pins and prints any fix.
1. Count the agent-rule commits your branch lacks. Use the remote for `udecode/plate`, `upstream` in a fork and `origin` otherwise: `git fetch <remote> next && git rev-list --count HEAD..<remote>/next -- AGENTS.md .agents .claude .codex`. When it prints more than 0, merge `<remote>/next` or rebase onto it, ask the human to start a new agent session with this skill, and stop here.
2. Apply each `fix:` the session-start check printed, in order. When this session shows none because its runtime ran no hook, run `node .agents/rules/contributor-setup/scripts/doctor.mjs` and apply what it prints until it prints `ok:`.
3. List your open PRs into `next` whose body check failed: `gh pr list --repo udecode/plate --author @me --base next --state open --json url,statusCheckRollup --jq '.[] | select(any(.statusCheckRollup[]; .name == "PR body" and .conclusion == "FAILURE")) | .url'`.
4. Rewrite each one's body the way `land.mjs` would. Save it with `gh pr view <number> --json body --jq .body > <file>`. When the PR changes exactly one plan under `docs/plans/`, render that plan into the file as the `plan-page` skill's PR section says, with `--into <file>`. Otherwise keep the body and add two sections. `## Why` holds a short paragraph on why the change exists. `## Verification` lists each command or check run on the PR's head with its outcome, and names what was not tested. When nothing has run yet, run the PR's focused tests first. End the body with a line that starts `Beyond the ask:` and names each change the request did not ask for, or says `none`. Update the PR with `gh pr edit <number> --body-file <file>`, and the check runs again. This step is done when step 3's command prints nothing.
Land later changes with `land.mjs`, as `.agents/pstack/rules/land.md` says. It opens the PR into `next` with the right body.
Files in this package (2)
- SKILL.md 2 KB
- scripts/doctor.mjs 5 KB
Versions
The database has no other skills named contributor-setup.
Database snapshot: 13.11.2026 · package version ff3bdd6daf8d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90open-pr
Bring the branch up to date, push it, open the pull request for an issue in the body shape of the repository, and watch CI. The implement-issue skill uses it. Use it directly when a branch is ready. - 100update-branch
Bring your branch up to date with the latest default branch (or the teammate branch it's based on) by merging it in. Use when someone says "my branch is out of date", "get the latest changes", "sync with main", or a PR says it's behind or has conflicts. - 100contributor-docs-nav
Run the CONTRIBUTOR-DOCS nav script to update breadcrumbs and TOCs, and handle link verification. Use when updating contributor docs structure, regenerating navigation, or fixing broken links. - 100review-prs
Use when the user asks to review one or more GitHub pull requests — "review PR #12", "review the open PRs", "check the PRs the agents opened" — in Claude Code, Codex, or any other agent. Not for reviewing uncommitted local changes. - 100shepherd-prs
Automate shepherding, checking status, updating branches, and landing open PRs or approved third-party contributor PRs in the flutter/flutter repository using the gh CLI. When to use: - When you need to check the status of open PRs or shepherded third-party PRs. - When you need… - 98triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check…