changelog-automation
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
newProject & Program ManagementOperations & Supply ChainAI & Automation
Changelog Automation
Patterns and tools for automating changelog generation, release notes, and version management following industry standards.
Use this skill when
- Setting up automated changelog generation
- Implementing conventional commits
- Creating release note workflows
- Standardizing commit message formats
- Managing semantic versioning
Do not use this skill when
- The project has no release process or versioning
- You only need a one-time manual release note
- Commit history is unavailable or unreliable
Instructions
- Select a changelog format and versioning strategy.
- Enforce commit conventions or labeling rules.
- Configure tooling to generate and publish notes.
- Review output for accuracy, completeness, and wording.
- If detailed examples are required, open
resources/implementation-playbook.md.
Safety
- Avoid exposing secrets or internal-only details in release notes.
Resources
resources/implementation-playbook.mdfor detailed patterns, templates, and examples.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Details
| Source | community |
|---|---|
| License | — |
| Risk label | critical ("critical" means the skill may run commands or touch files — read before use) |
| Files | SKILL.md, resources/implementation-playbook.md |
| Added | 2026-02-27 |
Related skills
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
ai-loop
Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.
airflow-dag-patterns
Build production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
antigravity-workflows
Use when asked to ship a SaaS MVP, audit application security, build an AI agent, run browser QA, or design a domain model with multiple skills and verified checkpoints.
ask-questions-if-underspecified
Clarify requirements before implementing. Use when serious doubts arise.