Menu
Edit changelog using git commit history via script.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | edit-changelog |
| description | Edit changelog using git commit history via script. |
GOAL: generate changelog entries from git history and update
CHANGELOG.md.
WHEN: the agent needs to update the changelog with recent commits.
NOTE: requires CHANGELOG.md and .last-aggregated-commit
(auto-initialized).
scripts/edit-changelog.shERROR: Stop and report to userWARN: Report no changes neededSUCCESS: Report success with entry countDONEFiles modified:
CHANGELOG.md - Unreleased section updated.last-aggregated-commit - Updated to HEADStatus communication:
First line of output indicates status:
SUCCESS: [message] - Operation completed with changesWARN: [message] - Operation completed but no changes neededERROR: [message] - Operation failedThe following reference files serve as strict guidelines:
references/keep-a-changelog-spec.md: Format specificationreferences/changelog-templates.md: Template variationsreferences/changelog-structure.md: Structure documentationreferences/aggregation-patterns.md: Aggregation patternsPresent the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs.
Fix lint, formatting, and prose issues in markdown files using Prettier and Vale. Use when the user or agent needs to fix lint, formatting, and prose issues in markdown files.
Autonomously select files to stage for an atomic Git commit. Use when the agent wants to stage selected files for a git commit. Only stages selected files, but does not commit them.
Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills in sequence to perform the commit.
Generate a commit message for changes already in the Git staging area, and await approval from the user. Use when the agent needs to generate a commit message for staged changes. Only generates the commit message, but does not perform the commit.
Creates a new agent skill. Use when agent or user needs to create a new skill for the agent.