跳到正文
cccskills
免费在 GitHub 公开

changelog-entry

Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Instructions

  1. Find the most recent git tag:

    git describe --tags --abbrev=0
    

    If a tag exists, list commits since that tag:

    git log --oneline --no-merges <last-tag>..HEAD
    

    If no tag exists (the repository has no releases yet), list all commits:

    git log --oneline --no-merges
    
  2. Read each commit subject line and classify it into one of the Keep a Changelog sections:

    • Added — new features, new files, new API endpoints, new configuration options
    • Changed — changes to existing behavior, updated dependencies, modified defaults
    • Fixed — bug fixes, corrected behavior, resolved errors
    • Removed — deleted features, removed files, dropped API endpoints
    • Deprecated — features that still work but are marked for future removal
    • Security — vulnerability patches, authentication improvements, permission changes

    Ignore merge commits, version bump commits, and changelog update commits. Ignore commits whose subject line is obviously tooling noise (dependency lock file updates with no semantic change, CI config tweaks that do not affect users).

  3. Write the entry in Keep a Changelog format:

    ## [Unreleased]
    
    ### Added
    - Description of added thing
    
    ### Changed
    - Description of change
    
    ### Fixed
    - Description of fix
    

    Omit sections that have no entries.

    Write each bullet in present tense, starting with a verb: "Add", "Fix", "Remove", "Update". Do not start bullets with the commit type prefix (feat:, fix:, etc.) — strip those and rephrase.

  4. Output only the new CHANGELOG block. Do not output any surrounding explanation.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

Create a git branch named after a GitHub issue.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.

中文简介正在准备中。当前显示原文说明。

davila7/claude-with-skills132026年5月15日 更新

查看 davila7 的全部技能

报告此技能的问题