菜单
Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/abhinav/home --skill changie命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | changie |
| description | Use when deciding whether a repository change needs a changelog entry, creating or updating Changie unreleased entries, choosing the correct changelog kind, or writing user-facing changelog body text in repositories that use `.changie.yaml`. |
Use this skill only if the repository has a .changie.yaml file.
If .changie.yaml is absent,
this skill does not apply.
This skill covers how to use changie directly,
choose the correct kind from .changie.yaml,
and write changelog body text.
Add a changelog entry when the change is user-facing. Typical examples include:
Do not add a changelog entry for work that has no user-facing effect. Typical examples include:
Use changie directly by default:
changie new --kind $kind --body $body
Prefer generating the entry through Changie instead of hand-writing the file. That preserves the expected filename, timestamp, and directory layout.
Read the allowed kinds from .changie.yaml.
Common kinds include:
AddedChangedDeprecatedRemovedFixedSecurityChoose the kind based on the user-visible outcome, not the implementation detail.
Examples:
Added.Changed.Fixed.Deprecated.Removed.If .changie.yaml defines custom kinds,
use those instead of generic assumptions.
The body should describe the user-facing effect.
.changie.yaml.Good bodies usually answer: "What changed for the user?"
Weak bodies usually describe only internal work, for example:
refactor API clientcleanupmove code into helperThose are engineering notes, not release notes.
If changie is not found,
look for repository-specific wrappers before doing anything else.
Check:
mise.tomlMakefileIf either file defines a wrapper for running changie,
use that wrapper instead of assuming a global changie binary exists.
Mandatory for Git repository operations involving commits, amendments, fixups, branch creation or movement, stacked branches, pushes, pull request creation, pull request updates, pull request merges, review submission, publishing, or recovery from raw Git usage. Use git-spice for supported operations; do not bypass git-spice for commits, branches, stack movement, pushes, pull request submission, or pull request merging.
Use when the user explicitly requests a Pikchr diagram, Pikchr source, a `.pikchr` file, or SVG rendered with Pikchr. Do not use for a general diagram request that does not select Pikchr as the format.
Use when drafting, revising, evaluating, reviewing, or applying a commit message; or when committing work, amending commits, creating fixup commits, creating branches as part of committing work, stacking work, inserting prerequisite work below the current branch, or recovering after raw Git commands. Do not use for general prose or code review that involves neither a commit message nor a commit operation.
基于 SOC 职业分类
