菜单
Use when you've made code changes and need to add a changelog entry. Analyzes git diffs to create changie fragment YAML files in the correct format for this project.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tylerbutler/shelf --skill add-changelog-entry命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | add-changelog-entry |
| description | Use when you've made code changes and need to add a changelog entry. Analyzes git diffs to create changie fragment YAML files in the correct format for this project. |
.changes/unreleased/This skill creates changelog entries for the shelf project using changie. Instead of running the interactive changie new command, it writes fragment YAML files directly to .changes/unreleased/.
Examine what has changed to determine what changelog entries are needed. Run:
# Check for staged changes first, fall back to unstaged, then recent commits
git --no-pager diff --cached --stat
git --no-pager diff --stat
git --no-pager log --oneline -5
Read the actual diffs to understand the nature of the changes:
git --no-pager diff --cached # staged changes
git --no-pager diff # unstaged changes
If no local changes are found, check the most recent commit(s) that don't have changelog entries yet.
Classify each distinct change into one of the following kinds (defined in .changie.yaml):
| Kind | When to use | Version bump |
|---|---|---|
| Breaking | API changes that break existing usage | minor (major after v1.0) |
| Added | New features, new public functions, new types | minor |
| Changed | Behavior changes to existing features | patch |
| Deprecated | Features marked for future removal | patch |
| Fixed | Bug fixes | patch |
| Performance | Performance improvements | patch |
| Removed | Removed features or public API | patch |
| Reverted | Reverted previous changes | patch |
| Dependencies | Dependency version changes | patch |
| Security | Security-related fixes | patch |
Draft a body for each entry. The body format is:
Short summary title on the first line
Optional longer description on subsequent lines explaining the change in more detail.
Multiple paragraphs are fine.
The first line becomes the ##### heading in the rendered changelog. Keep it concise but descriptive.
Writing guidelines:
(#42))Present the proposed entries and ask for confirmation before writing files. Show the kind, title, and body for each entry. Ask if any should be added, removed, or modified.
Write a Python script to create the fragment files. Each fragment is a YAML file in .changes/unreleased/ with the naming convention {Kind}-{YYYYMMDD}-{HHMMSS}.yaml.
#!/usr/bin/env python3
"""Create changie changelog fragment files."""
import os
from datetime import datetime
CHANGES_DIR = ".changes/unreleased"
def create_fragment(kind: str, body: str) -> str:
"""Create a changie fragment YAML file and return the file path."""
now = datetime.now()
timestamp = now.strftime("%Y%m%d-%H%M%S")
filename = f"{kind}-{timestamp}.yaml"
filepath = os.path.join(CHANGES_DIR, filename)
# Format the timestamp in Go's reference time format (changie convention)
# Example: 2026-03-22T21:32:46.808155106-07:00
iso_time = now.astimezone().isoformat()
content = f"""kind: {kind}
body: |-
{chr(10).join(' ' + line if line else '' for line in body.split(chr(10)))}
time: {iso_time}
"""
with open(filepath, 'w') as f:
f.write(content)
return filepath
# Example usage:
# create_fragment("Fixed", "Fix resource leak on table close\nETS table was not deleted when close() encountered a DETS sync error.")
Write a script like the above, customized for the specific entries needed, and run it with python3.
Important: If creating multiple entries, space them at least 1 second apart or use unique timestamps to avoid filename collisions.
After writing, verify the files:
# List new fragment files
ls -la .changes/unreleased/
# Show contents of newly created files
cat .changes/unreleased/{filename}.yaml
# Preview what the changelog will look like
changie batch auto --dry-run
Confirm the preview looks correct. If changie reports any errors, fix the YAML format.
kind: Added
body: |-
Short summary title
Optional longer description explaining the change.
time: 2026-03-22T21:32:46.808155106-07:00
kind: Must exactly match one of the kinds in .changie.yamlbody: Uses YAML block scalar (|-). First line is the title, rest is description. Each line indented 4 spaces.time: ISO 8601 timestamp with timezone offset