On any failure (non-zero exit or error field in JSON) print ⚠️ <error message> and stop.

Steps

Get context: .agents/skills/pflow-changelog/scripts/changelog-context.sh. It returns JSON {feature:{title,version}, tasks:[…], commits:"…"} or {error:{…}}.
Analyze the context (tasks + commit messages). Summarize what was done in product terms — no tech internals, no process/dev meta. Then compose a changelog entry using the format below and prepend it to the existing CHANGELOG.md (create the file if absent, starting with the standard header: # Changelog\n\nAll notable changes to this project will be documented in this file.).
Commit and push: .agents/skills/pflow-changelog/scripts/changelog-commit-push.sh. It prints {commit_hash, branch_name, push_status} or {…, error:{…}}. If error is present, print ⚠️ <error.message> and stop.

Reply exactly:

✅ Changelog updated for <feature_title> (<feature_version>).

Changelog format (Keep a Changelog)

Each version entry follows this structure:

## [<version>] - YYYY-MM-DD