Agent skill · software engineering · yonatangross
commit
Creates Conventional Commits with scope detection, co-author lines and hook compliance; blocks secrets and generated-only files. Use when asked to commit, save progress or write a commit message, not for incidental commits.
Why this skill is useful
Adds specific commands and validation checks for creating conventional commits that the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 6k tokens when loaded. Last updated 2026-08-06. 215 stars on the source repository.
What this skill does
Smart Commit Host-neutral workflow. Invoke by skill name (commit). Claude Code slash routing, YAML hook loaders, and .claude/chain live in references/claude-code.md. Simple, validated commit creation. Run checks locally, no agents needed for standard commits. Note: If disableSkillShellExecution is enabled (CC 2.1.91), the git repository check won't run. This skill requires a git repository. Quick Start Argument Resolution STEP 0: Choose Commit Mode (AskUserQuestion — M118 #1465) Default is "new commit", but voice-flow needs explicit choice when amend / push / stash is wanted: Mode-specific guards: Amend HEAD — verify HEAD is not on origin (git rev-list HEAD..origin/<branch> empty); if it is published, refuse and recommend "New commit" instead. New commit + push — re-check the protected-branch rule from Phase 1 before pushing; if HEAD's branch is main/master/dev, abort. Stash first — git stash push -k -m "ork:commit autostash" (keep-index), commit, then git stash pop after push success. Workflow Phase 0: Confirm there is a repository to act on Before any guard, run git rev-parse --is-inside-work-tree. If it fails, or if the Bash tool is not available in this session, say so in one sentence and produce the commit message text only. Skip Phases 1 to 3 entirely. Never print a branch guard, a validation status, or any other repository fact you did not observe. Measured with claude plugin eval on 2026-09-12: in a sandbox with no repository and no Bash, this skill rendered a "pre-commit guard" box claiming the branch was main and protected. Nothing had been checked. A message-only answer that says "I could not verify branch or lint state" is correct; an invented guard is a defect. Phase 1: Pre-Commit Safety Check Phase 2: Run Validation Locally Run every check that CI runs: Fix any failures before proceeding. Phase 3: Review Changes Phase 3b: Agent Attribution (automatic) Before committing, check for the branch activity ledger at .claude/agents/activity/{branch}.jsonl. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills yonatangross/commit--4ff6d5