Organize and document software releases with semantic versioning and standardized changelog formats.
Works with
Provides Keep a Changelog format with seven standard categories (Added, Changed, Deprecated, Removed, Fixed, Security, Unreleased) for consistent release documentation
Enforces semantic versioning rules (MAJOR.MINOR.PATCH) with clear guidance on when to increment each version component
Includes templates for user-facing release notes, migration guides for breaking changes, and API dep
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionchangelog-maintenanceExecute the skills CLI command in your project's root directory to begin installation:
Fetches changelog-maintenance from supercent-io/skills-template and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate changelog-maintenance. Access via /changelog-maintenance in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
88
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
88
stars
CHANGELOG.md:
# 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 user profile customization options
- Dark mode support
### Changed
- Improved performance of search feature
### Fixed
- Bug in password reset email
## [1.2.0] - 2025-01-15
### Added
- Two-factor authentication (2FA)
- Export user data feature (GDPR compliance)
- API rate limiting
- Webhook support for order events
### Changed
- Updated UI design for dashboard
- Improved email templates
- Database query optimization (40% faster)
### Deprecated
- `GET /api/v1/users/list` (use `GET /api/v2/users` instead)
### Removed
- Legacy authentication method (Basic Auth)
### Fixed
- Memory leak in background job processor
- CORS issue with Safari browser
- Timezone bug in date picker
### Security
- Updated dependencies (fixes CVE-2024-12345)
- Implemented CSRF protection
- Added helmet.js security headers
## [1.1.2] - 2025-01-08
### Fixed
- Critical bug in payment processing
- Session timeout issue
## [1.1.0] - 2024-12-20
### Added
- User profile pictures
- Email notifications
- Search functionality
### Changed
- Redesigned login page
- Improved mobile responsiveness
## [1.0.0] - 2024-12-01
Initial release
### Added
- User registration and authentication
- Basic profile management
- Product catalog
- Shopping cart
- Order management
[Unreleased]: https://github.com/username/repo/compare/v1.2.0...HEAD
[1.2.0]: https://github.com/username/repo/compare/v1.1.2...v1.2.0
[1.1.2]: https://github.com/username/repo/compare/v1.1.0...v1.1.2
[1.1.0]: https://github.com/username/repo/compare/v1.0.0...v1.1.0
[1.0.0]: https://github.com/username/repo/releases/tag/v1.0.0
Version number: MAJOR.MINOR.PATCH
Given a version number MAJOR.MINOR.PATCH, increment:
MAJOR (1.0.0 → 2.0.0): Breaking changes
- API changes break existing code
- Example: adding required parameters, changing response structure
MINOR (1.1.0 → 1.2.0): Backward-compatible features
- Add new features
- Existing functionality continues to work
- Example: new API endpoints, optional parameters
PATCH (1.1.1 → 1.1.2): Backward-compatible bug fixes
- Bug fixes
- Security patches
- Example: fixing memory leaks, fixing typos
Examples:
1.0.0 → 1.0.1: bug fix1.0.1 → 1.1.0: new feature1.1.0 → 2.0.0: Breaking change# Release Notes v1.2.0
**Released**: January 15, 2025
## 🎉 What's New
### Two-Factor Authentication
You can now enable 2FA for enhanced security. Go to Settings > Security to set it up.
### Export Your Data
We've added the ability to export all your data in JSON format. Perfect for backing up or migrating your account.
## ✨ Improvements
- **Faster Search**: Search is now 40% faster thanks to database optimizations
- **Better Emails**: Redesigned email templates for a cleaner look
- **Dashboard Refresh**: Updated UI with modern design
## 🐛 Bug Fixes
- Fixed a bug where password reset emails weren't being sent
- Resolved timezone issues in the date picker
- Fixed memory leak in background jobs
## ⚠️ Breaking Changes
If you're using our API:
- **Removed**: Basic Authentication is no longer supported
- **Migration**: Use JWT tokens instead (see [Auth Guide](docs/auth.md))
- **Deprecated**: `GET /api/v1/users/list`
- **Migration**: Use `GET /api/v2/users` with pagination
## 🔒 Security
- Updated all dependencies to latest versions
- Added CSRF protection to all forms
- Implemented security headers with helmet.js
## 📝 Full Changelog
See [CHANGELOG.md](CHANGELOG.md) for complete details.
---
**Upgrade Instructions**: [docs/upgrade-to-v1.2.md](docs/upgrade-to-v1.2.md)
# Migration Guide: v1.x to v2.0
## Breaking Changes
### 1. Authentication Method Changed
**Before** (v1.x):
\`\`\`javascript
fetch('/api/users', {
headers: {
'Authorization': 'Basic ' + btoa(username + ':' + password)
}
});
\`\`\`
**After** (v2.0):
\`\`\`javascript
// 1. Get JWT token
const { accessToken } = await fetch('/api/auth/login', {
method: 'POST',
body: JSON.stringify({ email, password })
}).then(r => r.json());
// 2. Use token
fetch('/api/users', {
headers: {
'Authorization': 'Bearer ' + accessToken
}
});
\`\`\`
### 2. User List API Response Format
**Before** (v1.x):
\`\`\`json
{
"users": [...]
}
\`\`\`
**After** (v2.0):
\`\`\`json
{
"data": [...],
"pagination": {
"page": 1,
"limit": 20,
"total": 100
}
}
\`\`\`
**Migration**:
\`\`\`javascript
// v1.x
const users = response.users;
// v2.0
const users = response.data;
\`\`\`
## Deprecation Timeline
- v2.0 (Jan 2025): Basic Auth marked as deprecated
- v2.1 (Feb 2025): Warning logs for Basic Auth usage
- v2.2 (Mar 2025): Basic Auth removed
CHANGELOG.md # Developer-facing detailed log
RELEASES.md # User-facing release notes
docs/migration/
├── v1-to-v2.md # Migration guide
└── v2-to-v3.md
#changelog #release-notes #versioning #semantic-versioning #documentation
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
supercent-io/skills-template
supercent-io/skills-template
supercent-io/skills-template
supercent-io/skills-template
supercent-io/skills-template
supercent-io/skills-template
Useful defaults in changelog-maintenance — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: changelog-maintenance is focused, and the summary matches what you get after install.
Keeps context tight: changelog-maintenance is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added changelog-maintenance from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
changelog-maintenance fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for changelog-maintenance matched our evaluation — installs cleanly and behaves as described in the markdown.
changelog-maintenance has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: changelog-maintenance is focused, and the summary matches what you get after install.
I recommend changelog-maintenance for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added changelog-maintenance from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 75