Results for “keep-a-changelog”

Generates and maintains CHANGELOG.md files following Keep a Changelog conventions — from git history, commit messages, or a description of changes. Use when asked to write a changelog, update release notes, or document what changed in a version.

Generate user-facing App Store release notes by collecting and summarizing user-impacting changes from git history since the last tag.

Generate changelogs from git history and validate conventional commits. Usage: /changelog <generate|lint> [options]

Generates a concise bullet-point summary of branch changes for a pull request description, grouping related commits by theme and verifying details against actual files.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Changelog Generator

changelog-generator

Analyzes git commit history and generates structured changelogs categorized by change type.

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

Use after a release succeeds, when maintainers need to sync apps/pythinker-code/CHANGELOG.md into docs/en/release-notes/changelog.md and docs/zh/release-notes/changelog.md, then open a PR on a dedicated branch.

Generates a single unified changelog from git history, written in plain language for the whole company, defaulting to Slovak and comparing the release branch against develop for unreleased changes.

Transforms technical git commits into polished, user-friendly changelogs by analyzing commit history, categorizing changes, and generating customer-ready release notes.

Investigate a problem, log it to the debug changelog, cross-check past issues, and suggest a non-duplicate fix.

Write changelogs and release notes that users actually read, with guidance on categorization, user-facing language, visuals, and distribution.

Manage feature manifests for code traceability. Use when creating new features, updating existing features, checking feature health, or exploring the feature-to-code relationship. Activates for manifest validation, feature creation, changelog updates, and traceability queries.

Write release notes, changelogs, migration guides, deprecation notices, and version announcements that communicate changes clearly to users and developers. Use when shipping a new version, deprecating features, or guiding users through breaking changes. Also trigger for 'release notes', 'changelog', 'migration guide', 'breaking changes', 'deprecation notice', 'version update', 'what's new', or 'upgrade guide'.

Generate consistent, auditable release notes from Conventional Commits, compute semantic version bumps, and enforce commit format linting.

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.

Generates the stable Galyarder Framework release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Changelog Generator

Transforms technical git commits into a clear, compact, user-friendly changelog. Use when preparing release notes, creating product update summaries, documenting changes for customers, or maintaining a public changelog page.

Archive multiple completed changes at once. Use when archiving several parallel changes.

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Unified Diary System: A context-preserving automated logger for multi-project development.

Unified Diary System: A context-preserving automated logger for multi-project development.

Unified Diary System: A context-preserving automated logger for multi-project development.

Manages semantic versioning and changelog documentation for Flutter projects, defining a structured process for recording additions, changes, and removals across backend and mobile releases.