Agent Skills › emavgl/oinkoin › commit

commit

GitHub

指导 Agent 按照 Conventional Commits 规范创建 Git 提交，包括审查变更、选择相关文件、生成符合风格的提交信息，并严格禁止添加自动生成的署名或脚注。

.claude/skills/commit/SKILL.md emavgl/oinkoin

Trigger Scenarios

用户请求提交代码变更用户请求推送更改

Install

npx skills add emavgl/oinkoin --skill commit -g -y

More Options

Non-standard path

npx skills add https://github.com/emavgl/oinkoin/tree/master/.claude/skills/commit -g -y

Use without installing

npx skills use emavgl/oinkoin@commit

指定 Agent (Claude Code)

npx skills add emavgl/oinkoin --skill commit -a claude-code -g -y

安装 repo 全部 skill

npx skills add emavgl/oinkoin --all -g -y

预览 repo 内 skill

npx skills add emavgl/oinkoin --list

SKILL.md

Frontmatter

{
    "name": "commit",
    "description": "Creates commits using Oinkoin's conventional commit style without generated co-author or assistant footers.",
    "argument-hint": "[optional summary]"
}

Skill: commit

Use this skill when the user asks to commit or push changes.

Commit message style

Follow the repository's Conventional Commits style:
- feat: ... for new functionality
- fix: ... for bug fixes
- refactor: ... for code restructuring
- docs: ... for documentation
- test: ... for tests
- chore: ... for maintenance
Use lowercase type and a concise imperative summary.
Focus the summary on why the change exists, not a list of files.
Add a short body only when the motivation or impact needs clarification.
Do not add an issue number unless the user provides one.

Required footer policy

Do not add Co-Authored-By lines.
Do not add Co-authored-by lines with any capitalization.
Do not add Generated with, Generated by, assistant attribution, bot attribution, emoji, or similar generated footers.
Do not add any footer unless the user explicitly requests one.
The commit message must end after the summary or explanatory body.

Commit and push workflow

Review both staged and unstaged changes before committing.
Inspect recent commit messages and match their style.
Stage only files related to the user's request; leave unrelated pre-existing changes unstaged.
Check the staged diff and git diff --cached --check.
Create one focused commit unless the user asks for multiple commits or the changes are clearly independent.
Never force-push.
If pushing is rejected because the remote has new commits, stop and ask whether to rebase or merge; do not choose automatically.
Do not amend or rewrite an existing commit unless the user explicitly requests it.