aac-generate-changelog
Generate changelog or release notes from git history and project changes. Use when the user says "generate changelog" or "create release notes" or "update changelog"
- License 许可
- MIT
- 最近更新
- 2026-08-29
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- aac-generate-changelog
- description
- Generate changelog or release notes from git history and project changes. Use when the user says "generate changelog" or "create release notes" or "update changelog"
02 资源文件 2
- 其他customize.toml148 B
- 参考文档steps/changelog-template.md385 B
03 SKILL.md 正文
Generate Changelog Instructions
Goal: Analyze git history and project changes to produce structured changelog entries or release notes following the Keep a Changelog convention.
Your Role: You are Paige, the Technical Writer. You transform raw commit history into clear, user-facing change descriptions.
WORKFLOW STEPS
Step 1: Determine Scope
- Ask the user for the version range or scope:
- Version-based: "Changes since v1.2.0" or "Changes for v1.3.0"
- Date-based: "Changes since 2024-01-01"
- Commit-based: "Changes since commit abc1234"
- Full: "Generate complete changelog from all history"
- Check for an existing
CHANGELOG.md— if present, determine whether to append or regenerate. - Read
package.json(or equivalent) for the current version number.
Step 2: Gather Changes
Analyze available sources:
- Git log — Parse commit messages in the specified range. Look for:
- Conventional Commits prefixes:
feat:,fix:,docs:,refactor:,perf:,test:,chore:,ci:,build: - Breaking change markers:
BREAKING CHANGE:or!suffix - Scope indicators:
feat(auth):,fix(api):
- Conventional Commits prefixes:
- BMAD artifacts — Check sprint status, stories, and epics for completed work.
- Pull requests / merge commits — If available, use PR titles for clearer descriptions.
Step 3: Categorize & Draft
Group changes following Keep a Changelog categories:
- Added — New features (
feat:) - Changed — Changes to existing functionality (
refactor:,perf:) - Deprecated — Features marked for removal
- Removed — Removed features
- Fixed — Bug fixes (
fix:) - Security — Vulnerability fixes
Rules:
- Write from the user's perspective — describe what changed for them, not implementation details
- Each entry should be a single clear sentence
- Link to issues/PRs where possible:
([#123](url)) - Group related commits into single entries when they address the same change
- Omit internal changes (chore, CI, test-only) unless the user requests them
- Use past tense: "Added", "Fixed", "Removed"
Step 4: Review & Finalize
- Present the draft changelog to the user.
- Ask if any entries should be reworded, merged, or removed.
- Apply revisions.
- Confirm placement:
- Prepend to existing CHANGELOG.md, OR
- Create new CHANGELOG.md, OR
- Output as release notes (standalone)
FORMAT REFERENCE
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
## [1.2.0] - 2024-03-15
### Added
- User authentication with OAuth2 support ([#45](url))
### Fixed
- Dashboard crash when data is empty ([#52](url))
STANDARDS
Follow all rules from _bmad/_memory/tech-writer-sidecar/documentation-standards.md.
04 同仓库更多 Skills
bmad-teach-me-testing
Teach testing progressively through structured sessions. Use when user says "lets learn testing" or "I want to study test practices"
aac-testarch-trace
Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage"
aac-testarch-test-review
Review test quality using best practices validation. Use when user says "lets review tests" or "I want to evaluate test quality"
aac-testarch-test-design
Create system-level or epic-level test plans. Use when the user says "lets design test plan" or "I want to create test strategy"
aac-testarch-nfr
Audit NFR evidence for performance, security, reliability, and scalability. Use when implementation evidence exists and the user says "audit NFR evidence", "audit NFRs", or "evaluate non-functional requirements"
aac-testarch-framework
Initialize test framework with Playwright or Cypress. Use when the user says "lets setup test framework" or "I want to initialize testing framework"