Purpose and inputs
Advisory only. Do not bump versions, merge a release PR, or use publish credentials.
Steps
- Scope: Diff against
main(feature PR) or the previousv*tag (release PR). List payload paths (apps/api|web|mobile,packages/,tools/,scripts/,.cursor/,.agents/, generator). - Title: Suggest a conventional title (
feat/fix/perfor!/BREAKING CHANGE). Flagdocs/chore/test/ci/stylewhen payload paths changed unless the body hasskip-release: true. - Contract: Note generator CLI, template include/exclude, and docs snapshot impact. Generated trees must not gain the documentation app or the generator.
- Notes: Draft user-facing changelog bullets and required adopter actions. Keep Release Please's deterministic changelog authoritative.
- Evidence: Link tests, classification, and (on a release PR) scaffold acceptance. Stop if a human gate is missing (npm trusted publisher, GitHub App, who may merge).
Completion
Read completion evidence; return advisory findings without changing versions or publishing.