Commit
Personal agent skills (Claude Code / Codex) — SKILL.md collection
npx -y skills add YosukeIida/personal-agent-skills --skill commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 22 days oldThe repository was created 22 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
変更を conventional commits 規約でコミットする skill。「commitして」「コミットして」 「commit, pushして」「pushも」「それで commitして」などの指示、または /commit で発動。 差分を意味単位に分割し、リポジトリ既存のコミットスタイル（type/scope の使い方）を 踏襲したメッセージを生成する。指示に「push」が含まれれば push まで行う。
SKILL.md
1.8 KB, 514 tokens by cl100k_base, as published. Nobody here has run it
commit — 規約準拠コミット
手順
git status --porcelainとgit diff/git diff --stagedで変更の全体を把握するgit log --format='%s' -15で当該リポジトリの type/scope 慣習を確認し、それを踏襲する （例: dotfiles はfeat(skills):chore(claude):、llm-kie はfix(scripts):docs(paper):）- 変更が複数の関心事にまたがる場合は意味単位に分割して複数コミットにする
- メッセージは conventional commits 形式
type(scope): 要旨。本文には「何を」ではなく 「なぜ」を書く（差分を見れば分かることは書かない） - ユーザーが push を求めた場合のみ push する
（
git push。上流未設定ならgit push -u origin <branch>）
守ること
- main / master への force push はしない
- 無関係な untracked ファイルを勝手に含めない（明らかな残骸なら指摘だけする）
- pre-commit フック等が失敗したら、勝手に迂回（--no-verify）せず報告する
- diff に secrets らしきもの（.env、*.pem、credentials、API キー文字列）が含まれていたら コミットせず停止して確認する
- 別セッション・別作業由来と思われる変更が混ざっていたら、自分の変更だけを選んで stage する
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 1 of the 12 instructions most pr commit review skills give in 514 tokens
Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07
- Use conventional commits formathere, and in 127 of 888, across 115 files
- Keep subject line under 72 charactersin 62 of 888, across 48 files
- Delete branches after mergein 51 of 888, across 38 files
- Use imperative mood in subject linein 51 of 888, across 42 files
- Use imperative mood in commit messagesin 44 of 888
- Verify directory is ignored before creating worktreein 43 of 888, across 12 files
- Generate a conventional commit messagein 43 of 888
- Add unignored worktree directories to gitignorein 42 of 888, across 10 files
- Make atomic commitsin 39 of 888, across 27 files
- Run tests before committingin 36 of 888, across 25 files
- Verify clean test baselinein 35 of 888, across 9 files
- Split unrelated changes into separate commitsin 35 of 888, across 30 files
Said here and by no other author read
- check recent commit history for type and scope conventions
- stage only changes from your own session
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.