메뉴
Generates changelogs and creates tagged releases. Use when updating changelogs, preparing releases, or tagging versions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | changelog |
| description | Generates changelogs and creates tagged releases. Use when updating changelogs, preparing releases, or tagging versions. |
| license | MIT |
| context | fork |
| agent | general-purpose |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(git *), Bash(gh *) |
| argument-hint | [version] |
Every invocation creates a versioned release. Gathers commits since the last tag, writes a dated release entry in CHANGELOG.md, commits, tags, and pushes. Follows Keep a Changelog format and Conventional Commits conventions.
git status --porcelain must return empty (CHANGELOG.md exempt). If dirty, abort and tell the user to commit or stash first.git fetch origingit rev-list --count HEAD..origin/$(git branch --show-current). If behind, abort and tell the user to pull first.If $ARGUMENTS contains a version (e.g., v1.2.0), use it directly.
Otherwise, auto-detect from commits since the last tag:
git tag --sort=-v:refname | head -1
If no tags exist, treat the current version as 0.0.0.
Scan commits: git log --pretty=format:"%s%n%b" <last-tag>..HEAD. Apply the highest-priority rule:
| Priority | Signal | Bump |
|---|---|---|
| 1 | Breaking change — BREAKING CHANGE in body/footer, or type! suffix (feat!, fix!) | Major |
| 2 | New feature — feat or feat(scope) prefix | Minor |
| 3 | Bug fix or improvement — fix, perf, or other included types | Patch |
If all commits were filtered (docs, test, ci, chore only), report "No release needed" and stop.
Report the detected version before continuing:
Next version: X.Y.Z (bump — reason)
Commits since vCURRENT: N total (N included, N filtered)
git tag -l vX.Y.Z. If the tag already exists, abort and report the conflict.
git log --oneline <last-tag>..HEADci:, chore:, test:, docs:, and style: commits. For refactor: commits, include only when the diff touches a public API, CLI flag, configuration schema, or user-facing output; otherwise drop.git remote get-url origin).## [X.Y.Z] - YYYY-MM-DD with today's date, placed above existing version sections.git add CHANGELOG.mdgit commit -m "Release vX.Y.Z"git tag -a vX.Y.Z -m "Release vX.Y.Z - <one-line summary of changes>"git push --follow-tagsgit ls-remote --tags origin | grep vX.Y.Z and report the version, tag, and commit hash.Map Conventional Commits prefixes to Keep a Changelog sections. See references/changelog_format.md for the full mapping, writing style, and anti-patterns.
| Commit Prefix | Changelog Section |
|---|---|
feat: | Added |
fix: | Fixed |
refactor: (user-visible) | Changed |
security: | Security |
docs:, test:, ci:, chore: | Filter out |
Always include: features, user-facing bug fixes, breaking changes, security fixes. Always filter: merge commits, internal refactors, test changes, CI config, typos.
Translate technical commits to user-friendly language:
fix(auth): resolve JWT expiry edge case -> "Fixed session timeout issues for long-running sessions"feat(api): add /users endpoint -> "Added user management API endpoints"# All commits since last tag
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD
# Commits between tags
git log --oneline v1.0.0..v1.1.0
# Current tags
git tag --sort=-v:refname | head -10
# Changelog
All notable changes to this project will be documented in this file.
## [1.1.0] - 2026-02-13
### Added
- New feature description
### Changed
- Modified behavior description
### Fixed
- Bug fix description
## [1.0.0] - 2026-02-01
### Added
- Initial release features
[1.1.0]: https://github.com/owner/repo/compare/v1.0.0...v1.1.0
[1.0.0]: https://github.com/owner/repo/releases/tag/v1.0.0
| File | Content |
|---|---|
references/changelog_format.md | Full Keep a Changelog spec, Conventional Commits mapping, writing style guide, anti-patterns, release workflow reference, complete example |
Guides users through creating effective Claude Code skills with specialized knowledge, workflows, and tool integrations. Use when users want to create a new skill, update an existing skill, extract business logic into reusable packages, or ask about skill structure, frontmatter, or bundled resources.
Extracts text and tables from PDFs, creates new documents, merges/splits files, fills forms, and converts markdown to PDF. Use when working with PDF files, when the user mentions PDFs, document extraction, form filling, OCR, or markdown-to-PDF conversion.
Creates, edits, and analyses PowerPoint presentations with layouts, speaker notes, and design elements. Use when working with .pptx files, creating presentations from topics, modifying slides, or extracting content. Triggers: 'create presentation from topic', 'slide deck from document', 'powerpoint from scratch'.
Audits a codebase for production readiness across six dimensions: API completeness, frontend-backend sync, security, scalability, infrastructure, and dead code/architecture. Use when asked for a launch assessment, production readiness check, pre-deployment audit, or multi-agent patchwork cleanup.
Guides README creation and improvement with audience-matched templates. Use when writing READMEs for open source, personal, internal, or config projects, or when the user mentions documentation, README, or project setup.
Guides Remotion video development in React, including compositions, animations, timing, audio, captions, and rendering. Use when the user works with Remotion, writes <Composition>/<Sequence>/interpolate/spring, edits remotion.config.ts, renders or deploys Lambda videos, or asks about video creation in React.