Maintain CHANGELOG.md — add new version entries, keep the Unreleased section, cut a release, or restructure the whole file — following the Keep a Changelog format and Semantic Versioning.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this skill when the user wants to add a new version entry to a CHANGELOG.md, maintain the Unreleased section, cut a release, or restructure the changelog following the Keep a Changelog format and Semantic Versioning.
git log output.YYYY-MM-DD). Write plainly — many readers are not native speakers.date +%Y-%m-%d).Pin the link to the spec version the file follows (2.0.0 unless the repo pins an older one):
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/2.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- ...
## [1.1.0] - 2025-06-01
### Added
- ...
### Fixed
- ...
[Unreleased]: https://github.com/owner/repo/compare/v1.0.0...HEAD
[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
[Unreleased] compares the latest tag to HEAD; each version links to the diff vs the one before it; the oldest version links to its tag (nothing earlier to compare). Keep the link out of the heading so the file reads cleanly.
As notable changes land, append them to ## [Unreleased] under the right section. This is the default ongoing workflow.
## [Unreleased] to ## [X.Y.Z] - YYYY-MM-DD (heading and its link at the bottom).[Unreleased] link to compare the new tag against HEAD; add the new version's comparison link.## [Unreleased] section pointing at HEAD.date +%Y-%m-%d — never hardcode.CHANGELOG.md to identify the last released version and its date.git log --oneline <last-tag>..HEAD. If no tag exists for the last version, use git log --oneline and filter manually.Unreleased section, consistent section names/order, comparison links at the bottom, consistent bullet style (capital letter, no trailing period).date +%Y-%m-%d where a version claims today.Use only these six sections, in this order when multiple are present. Omit any empty section.
| Section | When to use |
|---|---|
| Added | New features or capabilities |
| Changed | Changes to existing behavior |
| Deprecated | Features marked for future removal |
| Removed | Features removed in this release |
| Fixed | Bug fixes |
| Security | Security-related fixes or improvements |
Fixed vs Changed — the decision rule: was the old behavior a bug? If yes → Fixed. If it was intentional and you changed it → Changed.
Dependencies are not a type of change. A dependency update can be harmless, a fix, or breaking — describe its effect under the right type, or leave it out.
Breaking changes — mark with **Breaking:** at the start of the entry, inside its type (usually Changed or Removed), never a separate section:
### Changed
- **Breaking:** `parse()` now returns a result object instead of raising.
- Rename the `color` option to `theme`.
CVEs — lead the entry with the CVE ID so readers and tools can match it:
### Security
- CVE-2024-12345: out-of-bounds read when parsing malformed input.
Deprecate before removing — mark Deprecated in one release, Removed in a later one, and say which version will remove it.
Yanked releases — list, don't hide: ## [0.0.5] - 2014-12-13 [YANKED].
This mapping assumes Conventional Commits messages produced by the git-commiter skill.
| Commit | Section |
|---|---|
feat: / add / new | Added |
refactor: / change / rename / move / update / improve | Changed |
fix: / bug / patch | Fixed |
remove: / delete / drop | Removed |
deprecate: | Deprecated |
security: / cve / vuln | Security |
docs: / chore: / ci: / test: | Omit unless user-facing |
When a commit is ambiguous, infer intent from the diff or file name. Remember: several commits often collapse into one entry — write for the reader, not the history.
Add retry logic for HTTP requestssimple-english skill.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
日本語の概要は準備中です。原文の説明を表示しています。
Execute git commits using the Conventional Commits specification. Use this skill whenever the user says "commit", "git commit", "/commit", "stage and commit", "make a commit", "save my changes", or asks to commit specific files or all changes. Also triggers on phrases like "push my changes" (commit first), "commit everything", "commit with message X", or whenever git diff/status suggests uncommitted work the user wants to save. Handles auto-staging, diff analysis, message generation, breaking change detection, batch splitting of unrelated changes, safe pushes, and pre-commit hook failures gracefully. Always use this skill rather than ad-hoc git commit commands.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
日本語の概要は準備中です。原文の説明を表示しています。
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a piece of work based on a spec or set of tickets.
日本語の概要は準備中です。原文の説明を表示しています。
Search and explore an Obsidian vault through the NoteBrain CLI (semantic search, tags, backlinks, connections, hidden links, boosted retrieval). Use it whenever the user mentions their notes, knowledge base, Obsidian vault, semantic search, finding connections or unlinked notes, or asks exploratory questions like "what do I know about X", "find notes related to Y", "what connects to Z", or "summarize my notes on W" — even when they never say NoteBrain, vector search, or ChromaDB.
日本語の概要は準備中です。原文の説明を表示しています。