Run any Skill in Manus with one click

changelog-generator

Stars2

Forks0

UpdatedJanuary 15, 2026 at 21:21

Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lexicalninja

lexicalninja/my-little-scrum-team

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	changelog-generator
description	Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.

Changelog Generator Skill

Instructions

Analyze git commits, pull requests, or code changes to identify what was modified
Categorize changes into: Added, Changed, Deprecated, Removed, Fixed, Security
Format entries following Keep a Changelog format (https://keepachangelog.com/)
Group related changes together
Use clear, concise language that users can understand
Include relevant issue/PR numbers when available
Maintain chronological order (newest first)
Add appropriate version headers and dates

Examples

Input: "Generate a changelog for the last 10 commits" Output:

## [1.2.0] - 2025-01-15

### Added
- New authentication flow with OAuth2 support
- User profile editing capabilities

### Changed
- Updated API rate limiting to be more permissive
- Improved error messages for validation failures

### Fixed
- Resolved memory leak in background job processor
- Fixed issue where deleted users could still receive emails

Input: "Create changelog entry for the payment module changes" Output:

## [Unreleased]

### Added
- Support for Stripe payment processing
- Payment retry logic for failed transactions

### Changed
- Payment webhook handling now uses async processing

Format Guidelines

Use semantic versioning (MAJOR.MINOR.PATCH)
Start with [Unreleased] for ongoing changes
Use present tense: "Add feature" not "Added feature"
Reference issues/PRs: "Fix login bug (#123)"
Group breaking changes under "### Changed" with migration notes

More from this repository

same repository

accessibility-checker

lexicalninja/my-little-scrum-team

Checks code for accessibility issues including missing alt text, poor color contrast, missing ARIA labels, keyboard navigation issues, screen reader compatibility, and focus management. Returns structured accessibility issue reports with WCAG compliance information.

2026-01-152

accessibility-design-checker

lexicalninja/my-little-scrum-team

Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.

2026-01-152

agent-capability-assessor

lexicalninja/my-little-scrum-team

Assesses agent capabilities by analyzing agent files and determining what tasks they can handle. Use when you need to evaluate if an existing agent can handle a task or if a new agent is needed. Reviews agent descriptions, skills, and workflows to determine capability match.

2026-01-152

agent-creator

lexicalninja/my-little-scrum-team

Creates new agent files with complete specifications, following the same format as existing agents. Use when a new agent is needed for tasks that existing agents cannot handle. Generates agent markdown files with name, description, core principles, workflow, and integration details.

2026-01-152

api-implementer

lexicalninja/my-little-scrum-team

Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.

2026-01-152

architecture-reviewer

lexicalninja/my-little-scrum-team

Reviews code architecture for design issues including poor separation of concerns, tight coupling, missing abstractions, design pattern violations, scalability concerns, and maintainability issues. Returns structured architecture review reports with improvement suggestions.

2026-01-152

name	changelog-generator
description	Generate changelog entries from git commits, pull requests, or code changes. Use when creating release notes, updating CHANGELOG.md, or documenting what changed in a version.

Changelog Generator Skill

Instructions

Analyze git commits, pull requests, or code changes to identify what was modified
Categorize changes into: Added, Changed, Deprecated, Removed, Fixed, Security
Format entries following Keep a Changelog format (https://keepachangelog.com/)
Group related changes together
Use clear, concise language that users can understand
Include relevant issue/PR numbers when available
Maintain chronological order (newest first)
Add appropriate version headers and dates

Examples

Input: "Generate a changelog for the last 10 commits" Output:

## [1.2.0] - 2025-01-15

### Added
- New authentication flow with OAuth2 support
- User profile editing capabilities

### Changed
- Updated API rate limiting to be more permissive
- Improved error messages for validation failures

### Fixed
- Resolved memory leak in background job processor
- Fixed issue where deleted users could still receive emails

Input: "Create changelog entry for the payment module changes" Output:

## [Unreleased]

### Added
- Support for Stripe payment processing
- Payment retry logic for failed transactions

### Changed
- Payment webhook handling now uses async processing

Format Guidelines

Use semantic versioning (MAJOR.MINOR.PATCH)
Start with [Unreleased] for ongoing changes
Use present tense: "Add feature" not "Added feature"
Reference issues/PRs: "Fix login bug (#123)"
Group breaking changes under "### Changed" with migration notes