Agent Skills › antiwork/gumroad › commit

commit

GitHub

指导 Agent 执行代码提交任务。包括检查变更、运行测试与 lint 确保质量、精准暂存文件，并遵循特定规范生成简洁的提交信息。

.agents/skills/commit/SKILL.md antiwork/gumroad

Trigger Scenarios

需要提交代码更改询问如何编写符合规范的 commit message

Install

npx skills add antiwork/gumroad --skill commit -g -y

More Options

Non-standard path

npx skills add https://github.com/antiwork/gumroad/tree/main/.agents/skills/commit -g -y

Use without installing

npx skills use antiwork/gumroad@commit

指定 Agent (Claude Code)

npx skills add antiwork/gumroad --skill commit -a claude-code -g -y

安装 repo 全部 skill

npx skills add antiwork/gumroad --all -g -y

预览 repo 内 skill

npx skills add antiwork/gumroad --list

SKILL.md

Frontmatter

{
    "name": "commit",
    "description": "Stage and commit changes with a clear, concise commit message.",
    "allowed-tools": "Bash(git *)",
    "argument-hint": [
        "optional message hint"
    ]
}

Commit

Create a commit for the current changes.

Steps

Run git status (without -uall) to see untracked and modified files.
Run git diff and git diff --cached to understand staged and unstaged changes.
Run git log --oneline -5 to see recent commit style.
Run bin/test-confidence to verify your changes don't break anything. Opus analyzes your diff and runs the right tests. Wait for 99% confidence (green bar) before proceeding. If any test fails, fix it first.
Run linters on changed files before staging:
- Ruby files: bundle exec rubocop --force-exclusion -a <files>
- JS/TS files: npm run lint-fast -- --max-warnings 0 --fix --no-warn-ignored <files>
- TypeScript type check: npx tsc --noEmit (required, catches type errors that eslint skips)
- CSS/SCSS/JSON/MD files: npx prettier --write <files>
- SVG files: npx svgo --multipass <files>
- Fix any lint errors or type errors before proceeding. Do not commit code that fails linting or type checking.
Stage the relevant files by name — avoid git add -A or git add ..
Write a commit message and commit.

If $ARGUMENTS is provided, use it as a hint for the message.

Commit message rules

Use the imperative mood ("Add", "Fix", "Remove", not "Added", "Fixes", "Removed").
Be concise: one short sentence, ideally under 50 characters.
Do NOT use conventional commit prefixes (no feat:, fix:, chore:, etc.).
Do NOT add any Co-Authored-By or similar trailers.
Focus on what changed and why, not how.
If a second line is needed for context, keep it brief.