kookaburra-pr-descriptions
Skill10 starsChanged 2 days agoApache-2.0View on GitHub
Writes pull request titles and descriptions for the Kookaburra Cut repo to one fixed, minimal standard. Use whenever opening a PR (gh pr create), writing or rewriting a PR description or PR body, or updating an existing PR's text. Triggers on "open a PR", "create a pull request", "PR description", "PR body", "update the PR".
- Commits and pushes
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- kookaburra-background-authoringSkill
- kookaburra-brand-packsSkill
- kookaburra-commitSkill
- kookaburra-export-presetsSkill
- kookaburra-lighting-authoringSkill
- kookaburra-releaseSkill
- kookaburra-scene-authoringSkill
- kookaburra-skill-creatorSkill
- kookaburra-video-editingSkill
The file
Files
kookaburra-pr-descriptions
One fixed shape for every PR description: a summary, a short What changed list, and a Verification line when the change gated. Bare essentials only; the code, docs and commit list carry the detail.
When to use
- Opening any PR in this repo (
gh pr create) - Writing, rewriting or updating a PR description
The standard
Title: conventional-commit form, type: lowercase imperative subject, under 72 characters (feat:, fix:, docs:, chore:, ...). It becomes the squash-merge commit, so write it as one.
Body: under ~120 words, Australian English, no em dashes (commas, colons, parentheses or full stops instead).
<One or two sentences: what this PR does and why it matters to a user of the repo.>
## What changed
- <4 to 6 bullets, each one shipped change>
- <deliberate behaviour changes and known limitations are bullets here too, e.g. "Transitions adjacent to a comparison blend the before side only">
## Verification
<ONE line, no hashes, the outcome `pnpm ready` printed: e.g. "pnpm ready READY: gate:merge EQUAL on both anchors, ws:device-video-spike EQUAL.">Omit ## Verification entirely when pnpm ready planned no gates (nothing on the export path changed), since CI covers the rest. Never add other sections.
Hard exclusions
Each of these has leaked into a real PR description before; the alternative is always available:
- No local paths, planning folders, worktrees or memory notes. PR #105 referenced a private planning folder that reviewers cannot see. Point to repo docs instead (
docs/comparisons.md,docs/determinism.md). - No internal work-package narrative. No "PR 3 of the ladder", batch numbers, or session history ("found along the way", "after the in-hand pass"). State what the PR does now, in the present tense.
- No commit-by-commit recounts. The PR's commit list already shows them.
- No baseline hashes. They live in
docs/determinism.md; the Verification line says the outcome ("gate:merge EQUAL", "new fixture Verify x2 identical"), not the bytes. - No screenshots or media attachments. A visual change gets a What-changed bullet describing it; reviewers see the pixels in the app and the gate fixtures.
- Never name the developer. No "Michael", no "the author". The PR describes the change, not the people.
- No private workspace names. The user's own
~/Kookaburra Cutprojects are private: no project, scene, product, client or people's names from them. Describe the case generically instead ("a large media-heavy project"). The pre-flight below greps for workspace folder names; also check for any project opened during the work.
Instructions
- Draft the body to the template above, writing it to a temp file (the scratchpad, never the repo).
- Pre-flight the draft and fix until clean:
wc -w <body-file> # aim under ~120 grep -iwFf <(ls ~/Kookaburra\ Cut | grep -v '^_' | grep -E '[0-9-]') <body-file> # must return nothing grep -nE "—|/Users/|worktree|batch [0-9]|PR [0-9] of|Michael" <body-file> # must return nothing - Open the PR:
gh pr create --title "type: subject" --body-file <body-file>. - Read the rendered PR back (
gh pr view) and confirm every reference resolves inside the repo.
Example
Title: feat: before/after comparison scenes
Adds before/after comparison scenes: one scene rendered as two sides under an animatable mask, with a scene kind, inspector drill and a divider timeline lane. Design record: docs/comparisons.md.
## What changed
- Compare engine: sidecar `compare` block, a second side host, masked composite on the transition target pools
- Mask family (linear, circle, radial, blend) with divider line, grip, label chips and tints
- Comparison scene kind, wizard flow and inspector drill with a Before/After pill
- Transitions adjacent to a comparison blend the before side only (said in the picker)
## Verification
pnpm ready READY: gate:merge EQUAL on both anchors, compare-spike EQUAL; new fixture Verify x2 identical in all four aspects.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

