菜单
This skill should be used when the user asks to "update the changelog", "add changelog entries", "what changed since last release", or when updating CHANGELOG.md with user-facing changes. Follows Keep a Changelog format and filters out internal-only commits.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing documentation, READMEs, explanations, blog posts, or any prose meant for humans to read
This skill should be used when the user asks to "rebase all open PRs", "update all PRs with latest main", "make sure every open PR is up to date with main", "sync all open PRs onto main", "rebase all my PRs", or wants to bring every open pull request current with its base branch by rebasing in parallel git worktrees, resolving conflicts with a team of agents, and force-pushing.
Groom and prioritize a project backlog — verify each candidate issue's claims against the current codebase, pick the most important N, rewrite them to a ready-to-work standard (Problem/Goals/Decisions/Outcomes/Verification), move them to Ready on the board, and close obsolete issues. Use when asked to "groom the backlog", "triage the backlog", "prioritize issues", "move issues to ready", or "what should we work on next".
This skill should be used when the user asks to "summarize a note", "summarize this article", "replace #summarize-later", "add a summary to a note", "generate takeaways", or mentions summarizing Obsidian notes. Replaces the #summarize-later tag with a high-level summary and actionable takeaways.
This skill should be used when the user asks to "improve a prompt", "make this prompt better", "optimize this prompt", "refine this system prompt", or wants to apply concept elevation to compress and clarify LLM instructions.
Use when writing, reviewing, or improving system prompts for AI tools, agents, chatbots, or LLM-powered products. Trigger phrases include "write a system prompt", "create a system prompt", "system prompt for X", "improve this prompt", "review my prompt", "prompt engineering".
| name | changelog |
| description | This skill should be used when the user asks to "update the changelog", "add changelog entries", "what changed since last release", or when updating CHANGELOG.md with user-facing changes. Follows Keep a Changelog format and filters out internal-only commits. |
Update a project's CHANGELOG.md with relevant user-facing changes since the last versioned release.
[Unreleased] section before adding entriesRead CHANGELOG.md and identify the most recent versioned release heading
(e.g., ## [0.5.1] - 2026-02-27). Extract the version tag (e.g., v0.5.1).
git log --oneline <tag>..HEAD
If the tag doesn't exist as a git tag, fall back to finding the commit whose
message contains the version string (e.g., chore(release): 0.5.1) and use
that commit hash instead.
For every commit, read the diff (git show --stat <hash> and git show <hash>
as needed) and classify it:
Skip internal-only commits. Only user-facing changes belong in the changelog.
Also skip any commit already represented in the existing [Unreleased] section.
Group changes under Keep a Changelog categories:
Only include categories that have entries. Place entries under the
## [Unreleased] heading, preserving any existing unreleased entries that are
still accurate.
Each entry should be a concise, user-oriented description of what changed and why it matters, not a restatement of the commit message.
If there are no user-facing changes to add, say so and do not modify the file.
If changes were added, show the user what was written to the [Unreleased]
section.