| name | lean-changelog |
| description | Turn findings-diff results into release-notes prose — short, honest "sustainability improvements in this release" sections for changelogs, release announcements, and internal newsletters. Use this skill whenever the user wants to communicate efficiency progress in a release, asks for changelog/release-notes text about green improvements, or wants findings-diff output made publicly legible. Part of Lean Agentic AI Skills; a transformer from diff results to publishable prose. |
Green Changelog
Transformer skill — the public-legibility layer. Input: findings-diff output (or two findings files to diff first), plus the publication venue (public changelog, internal notes, blog). Output: a short prose section ready to paste.
Progress that isn't communicated doesn't compound — teams stop investing in what leadership and users never see. But sustainability claims in public are exactly where inflated language does the most damage, so this skill writes with the module's tightest wording discipline.
Writing rules
- Lead with the countable. "This release resolved 3 efficiency findings, including converting all article images to AVIF (image transfer per page roughly halved — sizes in the release assets)." Counts, formats, and byte sizes from evidence are quotable; energy and carbon are not.
- Name the change, not the virtue. "Search results are now cached for repeat queries" beats "we care deeply about the planet". The venue's readers can judge significance from specifics; adjectives invite skepticism.
- The unmeasured stays visible in public too — a light-touch version: "…we haven't instrumented energy measurement yet; transfer sizes are our proxy." One clause, not a confession paragraph — but present. Public receipts with humility age well; ones without age badly.
- Regressions are mentioned when material. If the diff shows a new high-severity finding shipped in this release, an honest changelog says what's tracked for next release. Silence on regressions converts the changelog from record to marketing.
- Tone fits the venue — public changelog: 2-5 bullets, plain; internal newsletter: can carry the posture table and shout-outs; blog post: the story of one fix in depth beats a list of ten.
- Never retro-claim: only changes present in the diff between the two audited states are claimable in that release's section.
Output shape
A ready-to-paste markdown section titled for the venue's convention (e.g. "Efficiency & sustainability"), plus a one-line summary suitable for a release-tweet, both derived strictly from the diff data handed in.
Cost signal rendering
Countable cost claims are the only quotable numbers. Where the release resolved findings whose cost_signal.observed was measured before/after, those deltas ARE quotable in the changelog ("prompt tokens per call: 370 → 110"). Energy/carbon claims stay qualitative.
Not this skill's job
Computing the diff (findings-diff), full reports (lean-report-writer), ESG/compliance text (explicitly out — route to lean-report-writer's clearly-labeled ESG-flavored mode, and even that is not assurance-grade).
