菜单
Generate or update a CHANGELOG entry from git history since the last release, grouped by change type. Use when the user says "update the changelog", "add a changelog entry", "generate release notes", or is cutting a release and needs the CHANGELOG filled in.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/catRiceY/connectonion-studio --skill changelog命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Instrument code with structured logging or tracing to diagnose a runtime issue — spans around suspect calls, correlation IDs, timing, and key state at boundaries. Use when a bug only reproduces at runtime and the cause is unclear, when diagnosing why something is slow or intermittently fails, or when the user says "add logging", "add tracing", "instrument this", or "figure out what's happening at runtime".
Generate reference documentation for a project's public API or HTTP endpoints directly from the source — signatures, parameters, return values, status codes, and examples. Use when the user says "document the API", "write API docs", "document these endpoints", or wants a reference for public functions/routes.
Review a code diff or pull request for correctness, security, and style, reporting findings ranked by severity with concrete failure scenarios and fixes. Use when the user says "review this", "code review", "look over my PR", or asks to check a diff before merging.
基于 SOC 职业分类
正在显示 SKILL.md
| name | changelog |
| title | Update Changelog |
| description | Generate or update a CHANGELOG entry from git history since the last release, grouped by change type. Use when the user says "update the changelog", "add a changelog entry", "generate release notes", or is cutting a release and needs the CHANGELOG filled in. |
| category | version-control |
| tools | ["Bash(git log *)","Bash(git tag *)","Bash(git describe *)","Bash(git diff *)","read_file","edit_file","grep"] |
Turn commits since the last release into a human-readable CHANGELOG entry that matches the file's existing format.
Locate the changelog. Look for CHANGELOG.md, docs/CHANGELOG.md, HISTORY.md, or NEWS. Read the top of it to learn the exact format: heading style (## X.Y.Z — date), grouping (Added/Changed/Fixed/Removed vs custom sections), ordering (newest-first is standard), and language. Reproduce that style — do not impose "Keep a Changelog" if the repo uses something else.
Find the range. Determine the last released version:
git describe --tags --abbrev=0 for the most recent tag, or read the topmost version header in the changelog.git log <last-tag>..HEAD --no-merges --pretty=format:"%h %s".Determine the new version. Ask the user if unspecified, or infer from semver: breaking changes → major, new features (feat) → minor, fixes only (fix/chore) → patch. Note the project may have multiple independent release tracks — check RELEASING docs if present and confirm which track.
Classify each commit. Map commit subjects to changelog sections:
feat → Added / Features; fix → Fixed; perf/refactor → Changed; BREAKING CHANGE → a called-out Breaking section; docs/chore/test/ci → usually omit unless the repo lists them.Rewrite for humans. Each bullet should read as a user-facing outcome, not a raw commit subject. Strip the type prefix, use past-tense or noun phrases consistent with existing entries, and merge duplicates. Add issue/PR references ((#123)) if the repo does.
Insert the entry at the top (below any header/intro block) with edit_file. Include the version and today's date in the repo's exact header format. Preserve the --- separators, spacing, and any "Unreleased" section conventions.
Verify. Re-read the edited region to confirm formatting is intact and no existing entries were clobbered. Report the new version header and bullet count; do not commit or tag unless asked.