メニュー
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コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
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.
SKILL.md を表示中
SOC 職業分類に基づく
| 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.