flow-changelog-audit

The changelog audit scans the Claude Code CHANGELOG.md, builds an integration surface model, classifies entries as Adopt, Remove, or Adapt, and creates issues for approved items to track plugin integration impacts.

An integration surface model maps changelog updates to plugin-relevant changes by analyzing hooks, skills, agents, and surface APIs, categorizing them into Adopt, Remove, or Adapt classifications to determine necessary follow-up actions.

Changelog filtering is handled by analyzing new entries and mapping them to the integration surface model, isolating changes that specifically affect hooks, skills, agents, or surface APIs used by your plugin.

Yes, you can automatically create issues for approved items by running the audit, which files issues describing the change rationale and impact on the FLOW plugin directly within the source repository.

Yes, the changelog audit operates without external dependencies, relying entirely on the internal FLOW source repository and the Claude Code CHANGELOG.md to build the surface model and classify integration impacts.