메뉴
Generate a release changelog from git commits between the previous tag and HEAD. This skill should be used when the user wants to write release notes, generate a changelog, or summarize what changed since the last release.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | release-note |
| description | Generate a release changelog from git commits between the previous tag and HEAD. This skill should be used when the user wants to write release notes, generate a changelog, or summarize what changed since the last release. |
Generate a structured changelog from git history between the last tag and the current HEAD.
Arguments: <from-ref> (optional — defaults to the most recent v* tag)
git tag --list 'v*' --sort=-version:refname | head -1
<from-ref> is provided, use it instead.package.json to use as the release title.Run:
git log <from-ref>..HEAD --oneline --no-merges
Also collect merge commits separately for PR references:
git log <from-ref>..HEAD --oneline --merges
Split commits into two buckets: Features/Improvements and Bug Fixes.
| Bucket | Signals |
|---|---|
| Features / Improvements | feat, add, new, feature, implement, improve, enhance, update, refactor, optimize, perf, support |
| Bug Fixes | fix, bug, patch, resolve, correct |
Merge pull request #123), attach the PR number to the corresponding commits.This is the most important step. Do NOT list feature commits flat.
Output the changelog in this format:
## v{version}
### Features
- Headline for feature group A
- Specific change 1 (#PR)
- Specific change 2 (#PR)
- Headline for feature group B
- Specific change (#PR)
- Single-commit feature headline (#PR)
### Bug Fixes
- Description of fix (#PR if available)
- Description of fix (#PR if available)
Rules:
Display the formatted changelog to the user. Do not write it to a file unless asked.
Create a git tag from the version in package.json. This skill should be used when the user wants to tag a release, create a version tag, or tag the current commit for release.
This skill should be used when the user wants to file a GitHub issue, create a bug report, request a feature, report a problem, or open an issue in the current repository. It explores the codebase to understand project context, gathers issue details through conversation, and files the issue via the gh CLI. Trigger phrases include "file an issue", "create an issue", "report a bug", "request a feature", "open an issue", or "gh issue".
This skill should be used when the user asks to "create an agent", "write a subagent", "generate agent definition", "add agent to plugin", "write agent frontmatter", "create autonomous agent", "build subagent", needs agent structure guidance, YAML frontmatter configuration, invocation criteria with examples, or wants to add specialized subagents to Claude Code plugins with proper capabilities lists and tool access definitions.
Guide for building and maintaining ActivityPub/fediverse applications using Fedify. This skill should be used when users want to create federated social applications, implement ActivityPub protocols, build new features, test and debug federation, deploy to production, look up FEPs, or maintain existing Fedify applications.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.