What problem does it solve? Writing accurate change communication is hard: diffs show what changed but not why, test status is often assumed rather than verified, and public release notes can accidentally leak internal operational details. This Skill turns an explicitly scoped change set into one audience-appropriate artifact while preserving evidence status, risks, and unknowns. ## Core Features & Use Cases - Scoped change summarization: Works from a supplied diff, path set, commit range, PR range, or staged-only local changes, and states exactly what is included and excluded. - Evidence-state preservation: Distinguishes observed, reported, inferred, unknown, and conflicting claims so unverified tests or inferred intent are never presented as confirmed facts. - Four output profiles: Produces a PR description with reviewer context, public release notes, an operational release handoff, or a shareable summary, following repository templates when present. - Use Case: After staging a feature, ask for a PR description covering only the staged changes; the Skill excludes unrelated unstaged work, states that tests were not run, and redacts any suspected credentials found in the diff. ## Quick Start Ask the agent to write a PR description for the current staged changes, including impact, test status, and remaining risks.