release-notes

Generate release notes between two git tags and publish as a GitHub release. Input format: "<new-tag> from <base-tag>" (e.g. "v0.5.2 from v0.5.0").

跳到安装

仓库: griddynamics/specflow
最近来源活动: 2026年6月30日 09:29
检测到的 SKILL.md 语言: 英语
星标: 8
分支: 2

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/griddynamics/specflow --skill release-notes

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

creating-commits

Create well-structured git commits with clear, conventional commit messages. Use this skill whenever the user asks to commit changes, "commit this", "save my work", "make a commit", "write a commit message", or after completing a coding task when changes need to be committed. Also use when the user asks to split changes into multiple commits, amend a commit, or improve an existing commit message.

2026-07-07

backend-quality-gate

After substantive edits under backend/app, run static checks and optional Radon complexity (matches Makefile and Cursor post-write hook intent).

2026-06-30

deploy-requirements

Generate a customer-specific deployment requirements document from the template. Takes customer name and known infrastructure details as input. Produces a filled-in requirements spec ready for human review before sending to the customer.

2026-06-30

查看这个仓库的全部 Skills

Release Notes Generator

Steps

Parse args to extract NEW_TAG and BASE_TAG (format: v0.5.2 from v0.5.0).

Run git log <BASE_TAG>..<NEW_TAG> --oneline --merges to list merge commits (PRs).

For each merge commit, extract the PR number and title using gh pr view <number> --json number,title,author — match PR numbers from commit messages like #123 or Merge pull request #123.

If no PR number is found in a merge commit, use the commit subject as the entry with the committer as author.

Write release notes in the format below.

Publish the GitHub release: gh release create <NEW_TAG> --title "<title>" --notes "<body>".

If the tag does not yet exist on the remote, add --target main (or the default branch).
If the release already exists, use gh release edit <NEW_TAG> --notes "<body>" instead.

Print the release URL from the gh output.

Output Format

## <NEW_TAG> — <short label derived from the tag, e.g. "0.5.2"> <2-3 sentence Slack-ready summary. What shipped, why it matters, any breaking changes. Plain prose, no bullet points. No internal jargon.> ## What's Changed - <PR title> by @<author> in #<number> - <PR title> by @<author> in #<number> ... **Full Changelog**: https://github.com/<owner>/<repo>/compare/<BASE_TAG>...<NEW_TAG>

Rules

Derive <owner>/<repo> from gh repo view --json nameWithOwner -q .nameWithOwner.

Release title format: <NEW_TAG> (just the tag — GitHub prepends the repo name automatically).

The Slack summary goes at the top of the release body, before "What's Changed".

List only PRs merged between the two tags — do not include direct commits that have no PR.

If a commit has no associated PR, skip it silently unless it's the only change, in which case list it as - <subject> by @<author>.

Do NOT include "Merge branch" or "Merge pull request" boilerplate lines.

The summary must be usable as-is in a Slack message — no markdown headers, no code spans.

After publishing, print the final release URL so the user can share it.