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 で公開
commit-message
Generate a conventional commit message for the current staged git changes. Use when the user wants to commit, asks for a commit message, or asks what to write for a commit.
インストール方法を見る含まれるファイル（1）
- SKILL.md1.9 KB
SKILL.md（原文）
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Instructions
-
Run
git diff --stagedto see exactly what is staged for the next commit. -
Run
git status --shortto understand the full scope of changes (staged and unstaged) and identify the files involved. -
If nothing is staged, tell the user there is nothing staged and suggest they run
git addfirst. Stop here. -
Choose the correct Conventional Commits type based on the diff:
feat: a new feature or capability visible to users or callersfix: a bug fixdocs: documentation changes onlystyle: formatting, whitespace, missing semicolons — no logic changerefactor: code restructuring with no behavior change and no new featuretest: adding or correcting testschore: build system, dependency updates, tooling, CI config
-
Determine the scope from the changed files. The scope is optional but useful when the change is clearly isolated to one module, package, or layer (for example,
api,auth,db,cli). Omit it if the change is broad. -
Write the subject line:
- Format:
type(scope): descriptionortype: descriptionif no scope - Imperative mood: "add", "fix", "remove" — not "added", "fixes", "removing"
- Maximum 72 characters
- No period at the end
- Format:
-
If the diff is non-trivial (more than one logical change, or a change whose motivation is not obvious from the code), add a body:
- Blank line after the subject
- Bullet points explaining why the change was made, not what it does (the diff already shows what)
- Keep each bullet under 72 characters
-
Output only the commit message text. No surrounding explanation, no markdown code block wrapping.
レビュー
まだレビューはありません。使ってみた感想をお寄せください。
同じリポジトリのスキル
概要と使いどころ
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日 更新
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.
日本語の概要は準備中です。原文の説明を表示しています。
davila7/claude-with-skills132026年5月15日 更新