How do I install the Pflow Changelog skill?

Run npx skillmds@latest add phpinfo/pflow-changelog in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pflow Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pflow Changelog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pflow Changelog free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Pflow Changelog?

phpinfo (@phpinfo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pflow Changelog by phpinfo — Agent Skill

Name: Pflow Changelog
Author: phpinfo

File contents

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

### Added
- for new features.

### Changed
- for changes in existing functionality.

### Deprecated
- for soon-to-be removed features.

### Removed
- for now-removed features.

### Fixed
- for any bug fixes.

### Security
- in case of vulnerabilities.

Rules:

Use today's date (ISO 8601: YYYY-MM-DD).
Omit empty sections (e.g., skip ### Deprecated if nothing was deprecated).
Group changes under the most fitting category. Prefer ### Added / ### Changed / ### Fixed.
One bullet per notable change, concise, user-facing.
The changelog is for people, not machines. Focus on what changed and why from the user's perspective.

---name: pflow-changelogdescription: Generates a Keep a Changelog entry for the current feature version, prepends it to CHANGELOG.md, then commits and pushes. Requires clean working tree on the dev branch. Invoked manually only.license: MIT---On any failure (non-zero exit or `error` field in JSON) print `⚠️ <error message>` and stop.## Steps1. Get context: `.agents/skills/pflow-changelog/scripts/changelog-context.sh`. It returns JSON `{feature:{title,version}, tasks:[…], commits:"…"}` or `{error:{…}}`.2. 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.`).3. 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.4. Reply exactly: ```text ✅ Changelog updated for <feature_title> (<feature_version>). ```## Changelog format (Keep a Changelog)Each version entry follows this structure:```markdown## [<version>] - YYYY-MM-DD### Added- for new features.### Changed- for changes in existing functionality.### Deprecated- for soon-to-be removed features.### Removed- for now-removed features.### Fixed- for any bug fixes.### Security- in case of vulnerabilities.```Rules:- Use today's date (ISO 8601: `YYYY-MM-DD`).- Omit empty sections (e.g., skip `### Deprecated` if nothing was deprecated).- Group changes under the most fitting category. Prefer `### Added` / `### Changed` / `### Fixed`.- One bullet per notable change, concise, user-facing.- The changelog is for people, not machines. Focus on what changed and why from the user's perspective.

Frequently asked questions

Pflow Changelog