/add-changelog
Generate and maintain project changelog
$ npx -y skills add qdhenry/Claude-Command-Suite --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/add-changelog
Context preview
What this command does when you run it.
Generate and maintain project changelog
Command definition
add-changelog.mdAdd Changelog Command
Generate and maintain project changelog
Instructions
Setup and maintain changelog following these steps: **$ARGUMENTS**
1. **Changelog Format (Keep a Changelog)**
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- New features
### Changed
- Changes in existing functionality
### Deprecated
- Soon-to-be removed features
### Removed
- Removed features
### Fixed
- Bug fixes
### Security
- Security improvements
2. **Version Entries**
## [1.2.3] - 2024-01-15
### Added
- User authentication system
- Dark mode toggle
- Export functionality for reports
### Fixed
- Memory leak in background tasks
- Timezone handling issues
3. **Automation Tools**
# Generate changelog from git commits
npm install -D conventional-changelog-cli
npx conventional-changelog -p angular -i CHANGELOG.md -s
# Auto-changelog
npm install -D auto-changelog
npx auto-changelog
4. **Commit Convention**
# Conventional commits for auto-generation
feat: add user authentication
fix: resolve memory leak in tasks
docs: update API documentation
style: format code with prettier
refactor: reorganize user service
test: add unit tests for auth
chore: update dependencies
5. **Integration with Releases**
- Update changelog before each release
- Include in release notes
- Link to GitHub releases
- Tag versions consistently
Remember to keep entries clear, categorized, and focused on user-facing changes.
Read more
Add Changelog Command
Generate and maintain project changelog
Instructions
Setup and maintain changelog following these steps: **$ARGUMENTS**
1. **Changelog Format (Keep a Changelog)**
# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ## [Unreleased] ### Added - New features ### Changed - Changes in existing functionality ### Deprecated - Soon-to-be removed features ### Removed - Removed features ### Fixed - Bug fixes ### Security - Security improvements
2. **Version Entries**
## [1.2.3] - 2024-01-15 ### Added - User authentication system - Dark mode toggle - Export functionality for reports ### Fixed - Memory leak in background tasks - Timezone handling issues
3. **Automation Tools**
# Generate changelog from git commits npm install -D conventional-changelog-cli npx conventional-changelog -p angular -i CHANGELOG.md -s # Auto-changelog npm install -D auto-changelog npx auto-changelog
4. **Commit Convention**
# Conventional commits for auto-generation feat: add user authentication fix: resolve memory leak in tasks docs: update API documentation style: format code with prettier refactor: reorganize user service test: add unit tests for auth chore: update dependencies
5. **Integration with Releases**
- Update changelog before each release
- Include in release notes
- Link to GitHub releases
- Tag versions consistently
Remember to keep entries clear, categorized, and focused on user-facing changes.
A comprehensive development toolkit designed following Anthropic's Claude Code Best Practices for AI-assisted software development.
Repo: qdhenry/Claude-Command-Suite
Other commands on claude-command-suite.
- /boundary-bbcr-fallback
Execute automatic BBCR (Collapse-Rebirth Correction) when knowledge boundaries are exceeded or reasoning fails.
Open command - /boundary-detect
Analyze semantic position relative to knowledge boundaries to prevent hallucination and identify uncertainty zones.
Open command - /boundary-heatmap
Generate a visual heatmap of knowledge boundaries showing safe zones, risk areas, and semantic coverage.
Open command - /boundary-risk-assess
Evaluate the current risk level and provide detailed analysis of potential hallucination or reasoning failure.
Open command - /boundary-safe-bridge
Find and construct semantic bridges to safely navigate from current position to target concept without crossing dangerous boundaries.
Open command - /optimize-prompt
Takes an input prompt and returns ONLY a token-optimized version that preserves meaning while minimizing token count. Based on LLM tokenization principles: common words tokenize more efficiently, unusual words break into more tokens, and conciseness reduces cost.
Open command

