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（原文）
安装前可以查看交给 AI 代理的指令内容。
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日 更新