branches-and-pull-requests · git:20261103.f65486c · 2026-11-03 · sha256 84ab79247f637067

branches-and-pull-requests git:20261103.f65486cA

Immutable. This exact content never changes and is served at /api/v1/blob/84ab79247f637067.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5urtp5usvyhiwrzm/84ab79247f63706730a3bed3daf165055ec1b1863bdd183fbaca1e948fcc58f9.json

Then /plugin install branches-and-pull-requests@markdownregistry-5urtp5usvyhiwrzm in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.

---
name: branches-and-pull-requests
description: Branch naming (feature/, fix/, chore/), how labels and release notes follow from the branch, the pull request template, and how changes get merged in the template repository. Use when creating a branch, writing a commit or opening a pull request.
metadata:
  scope: repository
---

# Branches and pull requests

## The rule

Every change goes through a pull request against `main`. A branch ruleset rejects any branch name except `main`, `feature/...`, `fix/...`, `chore/...` and `dependabot/...`. The prefix sets the release notes label automatically (`.github/labeler.yml`), and `.github/release.yml` groups the generated notes by label. The maintainer reviews and squash-merges; nobody merges their own pull request.

| Prefix | For | Label | Release notes section |
| --- | --- | --- | --- |
| `feature/` | Something new for users of the template | `enhancement` | New features |
| `fix/` | Something that was wrong | `bug` | Bug fixes |
| `chore/` | Tidying, dependencies, docs, pipeline | none from the name | Other changes |

Changed files add labels too: `.github/**`, `Dockerfile` or `docker-compose.yml` add `build`; a change made only of Markdown or `docs/` adds `documentation`. Add `breaking-change` by hand when generated solutions or template options change in a way users will notice.

## Steps

1. Branch from an up-to-date `main`: `git switch -c fix/review-validation`. Short, lowercase, hyphenated.
2. Write commit messages as a sentence about the change, in the imperative: "Validate the star rating on update".
3. Open the pull request and fill in `.github/pull_request_template.md`: a two or three sentence summary, the linked issue, the type of change, and whether the shared layers are touched.
4. If shared layers, skills or repository setup changed, say so; the same change has to go to all five templates (`family-sync`).
5. Wait for every required check (`ci-pipeline`). Fix failures with new commits; don't force-push over review comments.

## Don't

- Push to `main`, or use any other branch prefix.
- Merge your own pull request.
- Bundle unrelated changes; they're easier to review apart.
- Add AI attribution lines or tool footers to pull request descriptions.

## Check

The labels appear on the pull request a few seconds after it opens, and every required check is green.