Commit

Skill kborovik/pilot-skills/pilot-plan/skills/commit

Claude Code plugin marketplace — sdd (spec-driven dev) and gh (GitHub workflow) plugins

Install

npx -y skills add kborovik/pilot-skills --skill commit

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

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.
4 stars4 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

Commit staged git changes w/ descriptive Conventional Commits message. Triggers when user asks to commit, save changes, or mentions GitHub commits. Phrasings: "commit", "save my changes", "commit this".

SKILL.md

2.9 KB, as published. Nobody here has run it

Commit staged changes w/ well-crafted message.

Process

Check staged changes:
- git diff --cached --stat → see what staged
- not staged → inform user and exit
- $ARGUMENTS provided → use as hint
Analyze changes:
- git diff --staged → review
- Identify added / modified / removed
- Understand purpose and scope
Check repo style:
- git log --oneline --max-count=10 → recent patterns
- Match existing style (prefixes, capitalization, format)
Generate message:
- Title: Conventional Commits → type(area): concise imperative description
  - type: fix, feat, refactor, chore, docs, test
  - area: affected module (e.g. <area>)
- Title ≤ 72 chars
- Complex changes → body after blank line

Create commit:

Heredoc → preserves formatting:

git commit --message "$(cat <<'EOF'
<title>

<optional body>
EOF
)"

Verify:
- git status → confirm clean state
- git log --max-count=1 → show created commit

Commit message format

Simple:

fix(server): add validation for email input

With body:

refactor(server): replace session-based auth with JWT tokens

- Replace session-based auth with JWT
- Add token refresh endpoint
- Update middleware to validate tokens
- Add tests for token expiration

Write-time glyph gate

Pre-publish: rg --pcre2 '[∀∃∴⊥∈∉∧∨≤≥≠≡¬]' <body> on commit body before §5 git commit; match → bail and rewrite per core:steno register before mutation.

Style

Apply core:steno to commit message body. Conventional Commits prefix (type(area):) and identifiers / paths / #refs / error strings / SHAs preserved verbatim.

Requirements

Conventional Commits: type(area): imperative description
Title completes: "This commit will..."
Only commit what's staged (not stage more)
not push unless explicitly requested
Match repo style if possible
Cite issue numbers if relevant (e.g. fix login bug (#42))

OUTPUT — "Next" block

Heading ## Next; 1–5 atomic items (one sentence each, no Reply prefix); positional dispatch (run <int> or run /<plugin>:<cmd> [args]). Commit lands → follow-up usually /gh:pr (open PR from this branch) or /gh:merge (if branch already has open PR) or resume work w/ more staged changes.

Canonical example after commit lands:

## Next

1. git push origin <branch> — publish the commit
2. /gh:pr — open a PR for the branch
3. /gh:merge — squash-merge if a PR is already open