| name | building-ledger-release-note |
| description | Generate policy-aligned PR summary and changelog text for Building Ledger changes with required scope, security, and test sections. |
Building Ledger Release Note
Use this skill when preparing:
- pull request descriptions
- changelog entries
- release notes for user-visible workflow changes
1) Required inputs
Collect this information first:
- Changed files and behavioral impact.
- Security/privacy impact (access, evidence, identifiers, public/private exposure).
- Tests run (exact commands and outcomes).
- Scope boundaries (what was intentionally not included).
2) Output requirements
Always produce these sections in order:
- Summary
- Scope (Included / Not included)
- Security and privacy notes
- Test plan (Automated / Manual QA checklist)
- Migration plan
Use short, literal language. No hype.
3) Guardrails
Do not claim:
- legal guarantees
- security guarantees that were not tested
- behavior changes that are not in changed files
If no migration is needed, write: No migration required.
4) Changelog format
For user workflow changes, emit concise entries with:
Added: ...
Changed: ...
Fixed: ...
Security: ...
Only include categories that apply.
Reference
Use references/pr-and-changelog-template.md.