Results for “changelog”

Collect pull requests between Ant Design versions and turn user-facing changes into Chinese and English changelog drafts. Filter internal changes, highlight release priorities, add contributor links, and update both changelog files after preview confirmation and format checks.

• Collecting changes between a release tag and a target branch
• Preparing Chinese and English release notes together
• Filtering internal changes and highlighting release priorities

Prepare Bifrost releases by turning Git history into release summaries and module changelogs. Coordinate version updates across dependent modules, document database migration risks, and include closed issues and outside contributor credits.

• Preparing changelogs for a Bifrost release
• Coordinating version updates across dependent modules
• Documenting database migration rollback limits

Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".

The English summary is being prepared. Showing the original description.

Parse git history and produce or update a CHANGELOG.md following the Keep a Changelog convention. Supports Conventional Commits, basic prefix conventions, and unstructured commit messages. Intelligently categorizes changes, detects breaking changes, links to PRs/issues, and handles both initial generation and incremental updates. **Triggers — use this skill when:** - User asks to "generate", "create", "update", or "write" a changelog - User mentions "CHANGELOG", "changelog", "release notes" - User says "document changes", "what changed since last release" - User wants to "prepare a release" and needs a changelog entry - User asks to "clean up" or "reformat" an existing changelog **Covers:** Any git-based project. Handles Conventional Commits (feat/fix/chore), Angular convention, basic prefixes (Add/Fix/Remove), and freeform commit messages. Outputs Keep a Changelog format with optional Common Changelog enhancements.

The English summary is being prepared. Showing the original description.

Prepare a CHANGELOG.md entry for a Storybook minor or major release. Collect changes from prereleases, filter out changes already backported to patch releases, select significant highlights, and combine them with the full change list.

• Prepare a changelog for a Storybook minor release
• Summarize major release highlights
• Consolidate changes from prereleases

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Build workflows that generate changelogs and release notes from commits, pull requests, and releases. Use Keep a Changelog formatting, standardize commit messages with Conventional Commits, and manage version numbers through Semantic Versioning rules.

• Automating changelog generation from commits and pull requests
• Standardizing team commit messages
• Setting up GitHub or GitLab release notes

Update a project's changelog using GitHub releases, git history, and code differences. Select changes that matter to users, match the existing format, and write concise entries for the requested release.

• Add the latest missing release entry
• Align changelog text with GitHub Releases
• Summarize changes between release tags

Prepare user-facing changelog entries for source code changes. The skill determines whether an entry is needed, classifies the change, writes a clear title, and uses the project CLI to create a JSON file tied to the pull request.

• Add a changelog entry for a bug fix
• Classify a new feature or behavior change
• Explain a breaking change and its replacement

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed since last release", this is the skill to use. Do NOT manually edit CHANGELOG.md without this skill — it ensures proper formatting, user-perspective writing, and website changelog sync. For full release workflows (Release PR review, tests, draft assets, publication, announcements), use /release instead.

The English summary is being prepared. Showing the original description.

Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".

The English summary is being prepared. Showing the original description.

Maintain a changelog following Keep a Changelog format. Covers entry categorization (Added, Changed, Deprecated, Removed, Fixed, Security), version section management, and unreleased tracking. Use when starting a new project that needs a changelog, adding entries after completing features or fixes, preparing a release by promoting Unreleased entries to a versioned section, or converting a free-form changelog to Keep a Changelog format.

The English summary is being prepared. Showing the original description.

Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.

• Preparing release notes for a new version
• Summarizing weekly or monthly product updates
• Writing app store update descriptions

Turn a weekly Markdown changelog into a branded video project with animated interface examples, Annie narration, captions, and background music. The workflow selects key updates and builds a 45–60 second square video, with rendering performed on request.

• Turn weekly release notes into a short video
• Demonstrate product updates with animated interface examples
• Prepare a branded update video with narration and captions

Turn Git history into release notes and recommend the next version based on commit types and breaking changes. Check commit formatting, filter changes by package, and generate Markdown or JSON for automated release workflows.

• Prepare release notes before publishing a version
• Determine the next version from commit history
• Check commit message formats before merging

Turn Git commits, records of code changes, into clear release notes for users. The skill groups updates by type, rewrites technical descriptions in plain language, and filters out internal work such as refactoring and tests.

• Preparing release notes for a new version
• Summarizing weekly or monthly product updates
• Writing app store update descriptions

Create changelog files for significant changes in a pull request, a proposed code change. Describe effects users will notice and organize entries by PR number and change type, such as features or fixes.

• Writing changelog entries for a pull request
• Separating new features from bug fixes
• Explaining changes in user-facing language

Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.

• Draft release notes from scan results
• Organize features, fixes, breaking changes, and security updates
• Prepare Markdown for a CHANGELOG or GitHub release

Standardize Chinese Git commit messages and changelogs using Conventional Commits, a structured message format. The skill provides writing rules and configuration examples for message checks, interactive commit entry, and automatic changelog generation.

• Standardizing Chinese commit messages across a team
• Checking commit formats with commitlint and husky
• Generating changelogs with Chinese section headings

Analyzes git commit history and generates professional changelogs with semantic versioning, conventional commit support, and multiple output formats (Keep a Changelog, Conventional, GitHub). Use when editing CHANGELOG.md, CHANGELOG.txt, or HISTORY.md files, preparing release notes, creating releases, bumping versions, updating changelog, documenting changes, writing release notes, tracking changes, version bump, tag release, or when user mentions "changelog", "release notes", "version history", "release", "semantic versioning", or "conventional commits".

The English summary is being prepared. Showing the original description.

Actualiza CHANGELOG.md en el formato Keep a Changelog, añadiendo los cambios actuales bajo la sección Unreleased. Úsalo cuando la persona pida actualizar el changelog, añadir una entrada al changelog o registrar lo que cambió para las notas de la versión (p. ej. "añade esto al changelog", "actualiza el CHANGELOG con estos commits").

The English summary is being prepared. Showing the original description.

CHANGELOG エントリ追加・バージョン計算。「CHANGELOG」「変更履歴」「changelog add」「version bump」「バージョン」「バージョンアップ」などのキーワードで自動適用。

The English summary is being prepared. Showing the original description.

Prepare REA changelogs and GitHub release notes from a fixed Git revision. Turn verified changes into clear user outcomes, preserve accurate contributor credit, and keep the release text aligned with Release Please, the automated release workflow.

• Drafting release notes from Git history
• Rewriting changes around their impact on users
• Verifying contributor credit and issue links

Prepare Ant Design releases by checking branches, version numbers, and existing changelogs, then creating a release pull request. After it is merged, the skill can run npm publish when explicitly requested.

• Prepare a release pull request
• Choose a patch or minor version increment
• Check version numbers against English and Chinese changelogs