Reviews Piper changes against this project's own rules — the pre-1.0 break-freely policy, the layering constraint, the no-cgo requirement, and the fixed status strings. Use when reviewing a diff, a PR, or a branch in this repo, in preference to a generic code review.
File a GitHub issue on this repo with the required title prefix and labels. Use when opening an issue, or when a finding during other work is worth tracking rather than fixing inline.
Cut a Piper release — choosing the version, the green-tip gate, tagging, verifying goreleaser's output, smoke-testing the published installer, and publishing notes. Use when asked to cut, tag, or publish a release, or to promote an RC to final.
Instructions for piperbox/piper: Read CLAUDE.md in full first — it is the authoritative source for coding principles, commands, constraints, layering, and branch/PR/issue workflow. This file only captures high-signal facts an agent would otherwise get wrong that aren't obvious from filenames or CLAUDE.md.