跳到正文
cccskills
免费在 GitHub 公开

changelog

Turn a selected range of commits or merged pull requests into release notes grouped by change type. Describe user-visible effects, link to supporting changes, and highlight breaking changes so readers can assess an upgrade.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

集成工具GitHub
查看安装方法

适用场景

  • Write release notes covering changes since the last tag
  • Summarize pull requests merged during a selected period
  • Highlight breaking changes before an upgrade

包含的文件(1)

  • SKILL.md2.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

changelog — write a changelog from a commit/PR range

Turn a range of history into a clear changelog entry that a user can read to decide whether and how to upgrade.

Gather the range

Establish the range first. Honor an explicit one ("since v1.2.0", "the last 10 commits", "PRs merged this week"); otherwise default to commits since the most recent tag (git describe --tags --abbrev=0 then git log <tag>..HEAD).

Collect the raw material yourself with sys_os_shell:

  • git log <range> --no-merges --pretty=format:'%h %s' for the commit subjects.
  • git log <range> --merges or gh pr list --search "merged:>=<date>" for PRs.
  • git diff <range> --stat to see the surface area, and gh pr view <n> for a PR's intent when a subject line is terse.

When a subject is unclear about user impact, dispatch the researcher (purpose: explore) to read the diff and report what actually changed for users — do not guess from the subject alone.

Group by change type

Use the Keep a Changelog categories, dropping any that are empty:

## <version or range> — <YYYY-MM-DD>

### Added
### Changed
### Deprecated
### Removed
### Fixed
### Security

Write each entry

  • One line per user-visible change, in the imperative or past tense, describing the effect on the user — not the internal mechanics.
  • Lead with the change, link the PR or commit in parentheses at the end.
  • Omit pure-internal churn (refactors, test-only changes, CI) unless it changes behavior. A changelog is for users, not a commit dump.
  • Call out breaking changes explicitly and point to the migration-guide skill if upgrade steps are needed.

Verify

Before finalizing, route the draft through the reviewer (purpose: review) when the changelog will ship — version numbers, "removed"/"breaking" claims, and flag names are exactly what a fact-check catches.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Test Omnigent’s native Antigravity integration with a live local server and the real agy CLI. Verify messages traveling between the web interface and terminal, mirrored replies, permission requests, interruption, session resumption, and process cleanup.

中文简介正在准备中。当前显示英语简介。

  • Testing message delivery from the web interface to agy
  • Checking terminal output against mirrored session replies
  • Verifying permission requests and interruption
omnigent-ai/omnigent1.1万2026年10月18日 更新

Test Omnigent’s Antigravity SDK integration against a live local server. Build test agents and run real conversations to check Gemini authentication, model selection, tool connections, and failures across the full execution path.

中文简介正在准备中。当前显示英语简介。

  • Test authentication and real Gemini responses
  • Verify tool connections and sub-agent delegation
  • Investigate model selection failures
omnigent-ai/omnigent1.1万2026年10月18日 更新

api-docs

免费

Create reference documentation directly from source code for public functions, classes, command-line commands, and endpoints. Organize parameters, defaults, return values, errors, and runnable examples, then check that the documentation matches the implementation.

中文简介正在准备中。当前显示英语简介。

  • Writing reference docs for a public module
  • Documenting command-line arguments and defaults
  • Adding minimal usage examples for an API
omnigent-ai/omnigent1.1万2026年10月18日 更新

Create an Omnigent agent directory using validated templates for configuration and instructions. Choose how the agent runs, then add web search, shell access, external tool connections, or subagents only when the task requires them.

中文简介正在准备中。当前显示英语简介。

  • Creating a minimal Omnigent agent
  • Configuring an agent with web search
  • Adding shell access or MCP tool connections
omnigent-ai/omnigent1.1万2026年10月18日 更新

Test Omnigent’s setup, help, and terminal interactions by driving the real CLI in an isolated environment. Capture rendered screens and compare checks before and after a change to establish whether a reported interface problem was fixed.

中文简介正在准备中。当前显示英语简介。

  • Reproducing a first-run setup problem
  • Inspecting menus in a narrow terminal
  • Checking help text and command visibility
omnigent-ai/omnigent1.1万2026年10月18日 更新

Test Omnigent’s GitHub Copilot SDK integration on a live local server. Build test agents, run real conversations, and inspect authentication, model selection, tool connections, policy enforcement, and leftover processes to investigate integration failures.

中文简介正在准备中。当前显示英语简介。

  • Checking Copilot authentication with a real conversation
  • Testing model selection and tool connections
  • Verifying sub-agent dispatch and policy enforcement
omnigent-ai/omnigent1.1万2026年10月18日 更新

查看 omnigent-ai 的全部技能

报告此技能的问题