Agent skill
edit-changelog
Edit changelog using git commit history via script.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/edit-changelog
SKILL.md
Edit changelog
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).
Efficiency directives
- Optimize all operations for token and context efficiency
- Batch operations on file groups, avoid individual file processing
- Target only relevant files
- Reduce token usage
Workflow
- Run
scripts/edit-changelog.sh - Capture status from first line of output
- Handle the status:
- If
ERROR: Stop and report to user - If
WARN: Report no changes needed - If
SUCCESS: Report success with entry count
- If
DONE
Output
Files modified:
CHANGELOG.md- Unreleased section updated.last-aggregated-commit- Updated toHEAD
Status communication:
First line of output indicates status:
SUCCESS: [message]- Operation completed with changesWARN: [message]- Operation completed but no changes neededERROR: [message]- Operation failed
References
The 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 patterns
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?