Write an Architecture Decision Record (ADR) document for a technical decision. Use when documenting a technical choice, architectural decision, or design decision.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
無料GitHub で公開
changelog-entry
Draft the changelog entry for all unreleased commits in Keep a Changelog format. Groups commits into Added, Changed, Fixed, Removed, and Security. Use before releasing a new version or when updating CHANGELOG.md.
含まれるファイル（1）
- SKILL.md2.0 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Draft a changelog entry for the current unreleased changes.
Step 1: Find the last release tag
!git describe --tags --abbrev=0 2>/dev/null || echo "none"
If the output above is none, there are no previous tags — include all commits in the log.
Step 2: Get the commits since the last tag
If a last tag was found:
git log <last-tag>..HEAD --oneline --no-merges
If no last tag was found:
git log --oneline --no-merges
Step 3: Categorize the commits
Group the commits into Keep a Changelog sections using these rules:
- Added: new features, new commands, new files, new endpoints
- Changed: modifications to existing behavior, refactors, renames
- Fixed: bug fixes, error handling improvements, incorrect behavior corrected
- Removed: deleted features, removed flags, dropped support
- Security: vulnerability fixes, dependency updates addressing CVEs, auth changes
Skip merge commits, version bump commits (e.g., "Bump version to 1.2.0"), and commits that only touch lock files.
If a commit is ambiguous, prefer the more specific category. If it touches multiple areas, list it under the primary one.
Step 4: Output the entry
Output only the markdown block, ready to paste into CHANGELOG.md under ## [Unreleased]. Do not include any surrounding prose.
Format:
## [Unreleased]
### Added
- Description of new feature (commit: abc1234)
### Changed
- Description of change (commit: def5678)
### Fixed
- Description of fix (commit: ghi9012)
Omit sections that have no entries. If there are no unreleased commits at all, output: No unreleased commits since the last tag.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
REST API design conventions for this codebase. Use when writing or reviewing API endpoints, route definitions, response formatting, or client code that calls the API.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Automatically format code files after every edit using Prettier and ESLint. Active in the background whenever Claude edits a file. Formatting is silent — no prompts, no output unless a formatter fails. Use when you want consistent formatting enforced automatically during a coding session.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Create a git branch named after a GitHub issue.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新
Run a comprehensive code quality audit covering security, performance, and maintainability. Use for quarterly audits, pre-release reviews, or when onboarding to a large codebase.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新