fls-changelog-verification

Compare spec diffs against src/changelog.rst entries and map changed paragraph IDs to :dp: anchors.

Updated Jan 30, 2026

Search Tags:#changelog #qa #verification #diff #spec #release-notes

Ready to run

npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-changelog-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fls-changelog-verification
Source: https://github.com/PLeVasseur/opencode-project-agents/tree/main/fls/skills/fls-changelog-verification
Command: npx skills add https://github.com/PLeVasseur/opencode-project-agents --skill fls-changelog-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelogs must remain in sync with specification changes to ensure releases communicate accurate updates and avoid confusion during reviews.

Core Features & Use Cases

Compare diffs between spec changes and changelog entries to identify all impacted sections.
Map changed content to changelog anchors and IDs (e.g., :dp: IDs) and verify correct attribution.
Flag missing references, outdated sections, or missing syntax changes and generate a remediation checklist for PRs.
Provide an upstream PR note that links validation results to the corresponding spec changes.

Quick Start

Run the fls-changelog-verification on the latest PR diff to ensure that src/changelog.rst accurately references the updated spec changes.

Frequently Asked Questions about fls-changelog-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify changelog entries match spec changes in a PR?▼

To verify changelog entries match spec changes, compare the diff range between specification modifications and changelog entries, map changed paragraph IDs to their closest anchors, and flag any missing references in the changelog file.

What is changelog verification for release notes?▼

Changelog verification is the process of ensuring release notes accurately reflect specification changes by mapping updated paragraph IDs to changelog anchors and identifying missing references or syntax changes before a release.

How do I map changed paragraph IDs to anchors in a changelog?▼

Mapping changed paragraph IDs to anchors involves identifying the diff range between spec changes and changelog entries, then matching each changed ID to the closest :dp: anchor to verify correct attribution in the changelog.

Does changelog verification work with RST format files?▼

Yes, changelog verification works with RST format files by checking that src/changelog.rst entries correctly reference updated specification changes and flagging any missing syntax changes or outdated sections.

Why are my changelog entries missing references to updated spec sections?▼

Changelog entries miss references to updated spec sections when the diff range between spec changes and changelog entries is not properly mapped, leaving new sections or updated paragraph IDs unattributed in the changelog file.

What is the best way to generate a remediation checklist for missing changelog references?▼

The best way to generate a remediation checklist for missing changelog references is to enumerate added or removed paragraph IDs, flag missing references and syntax changes, and produce actionable guidance linking validation results to upstream PRs.