sebastiaanwouters/dotagents

commit

Use when asked to create a git commit, split changes into commits, or write a commit message.

First seen Mar 18, 2026

Installation

$ npx skills add sebastiaanwouters/dotagents --skill commit

Summary

  • Use when asked to create a git commit, split changes into commits, or write a commit message.
  • Prefer small commits that are easy to review.
  • Follow this repo's commit message pattern when clear from recent history or touched-path history; otherwise default to conventional commits.
  • Never commit gitignored, ephemeral, generated, local-only, or secret files.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sebastiaanwouters/dotagents · top by installs.

npx skills add sebastiaanwouters/dotagents

Browse all from sebastiaanwouters/dotagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,922 B
  • docs SUMMARY.md 370 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 10 installs

SKILL.md

Commit

Goal: small commits. Easy review wins.

Start:

  • git status --short
  • git diff --stat
  • git diff
  • git log --oneline -n 20
  • If needed: git log --oneline -- <path>

Slice:

  • One concern per commit.
  • Split unrelated edits.
  • If diff feels big, split more.
  • Do not mix refactor + behavior change unless tiny and inseparable.
  • Leave unrelated work unstaged.

Stage:

  • Prefer explicit paths: git add path/to/file.
  • Avoid git add . and git commit -a in dirty trees.
  • If staged too much: git restore --staged <path>.
  • Review exact commit with git diff --cached --stat and git diff --cached.

Keep out:

  • Never commit gitignored files.
  • Never commit ephemeral files: logs, caches, temp output, build artifacts, local env files, editor junk, downloaded files.
  • When unsure: git check-ignore -v <path>.
  • If file looks generated or local-only, leave it out unless user explicitly wants it committed.

Message:

  • Infer pattern from recent commits first.
  • Prefer touched-path history over repo-wide history when it shows a clear style.
  • If project style is mixed or unclear, default to conventional commits.
  • Keep subject short, specific, imperative, no trailing period.
  • Safe defaults: feat(scope): add x, fix(scope): handle y, refactor(scope): simplify z, docs(scope): update w, chore(scope): clean up q.

Commit:

  • Commit only the reviewed slice.
  • After commit, verify with git show --stat --oneline HEAD.
  • If nothing clean and coherent to commit, say so instead of forcing one.