Skip to content
Skills Library
Programming · Automation

commit

/commit

[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.

Licence
MIT
Last repository change
20.10.2026

Assessment and security

92/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content27 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.

Original author description

[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.

How it works

SKILL.md has no level-two headings · 7 lines, 192 words

SKILL.md preview
---
name: commit
description: '[Git] Use when asked to commit, stage and commit, or save changes. --push also pushes.'
metadata:
  instruction-profile: concise
---

1. Commit requested changes only; preserve other work. Load project configuration and matching skill overlays; never reconfirm commit/push. Follow root-linked tracking when present; re-stage its edits before candidate checks and refresh affected evidence; never block on tracking.
2. Scan the exact pending commit content for secrets before committing; never commit credentials or .env files, and block on findings with redacted file/line/rule evidence. Run applicable checks; reuse unchanged passing evidence and stop on failures or unavailable required checks.
3. Resolve `commit.reviewMode` with `node .claude/scripts/lib/commit-review-policy.cjs --operation=commit --risk=<low|medium|high>`; follow its selection (default `$commit-review --fix-loop`, at most two rounds), unless current matching review evidence already exists.
4. Give the review the exact commit descriptor, including paths and `"amend":true` when applicable; require a matching review receipt or policy-eligible skip via `.claude/hooks/lib/review-receipt.cjs` before committing, and refresh evidence after changes.
5. Create and verify a concise conventional commit. Only when `commit.fixOriginTrailer: true`, add `Fix-Origin: feedback` (requested fix), `regression` (earlier defect), or `not-applicable` (not a fix) to new commits; never reword history to add it; amend only on an explicit amend request for this task's unpushed commit; push only when requested; route PR requests to `$pull-request` and report the result.

Versions

RepositoryScoreLicence
This page · duc01226/EasyPlatform92MIT
rmsaitam/skill-git-conventions100MIT
opsmill/infrahub100Apache-2.0
kdlbs/kandev100AGPL-3.0
vinta/hal-9000100MIT
restarter/lets-workflow100MIT
mickeyyaya/evolve-loop100Apache-2.0
friendlyinternet/nuxt-crouton100MIT
yonatangross/orchestkit100MIT

Database snapshot: 13.11.2026 · package version 37f0ee7daedf (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 96commit-and-push
    Creates atomic conventional git commits using git-agent and pushes changes to the remote repository. Use when the user asks to "commit and push", "commit with git-agent", or wants an atomic AI-generated commit followed by a push.
  • 90git-commit-push
    Commit and push repository changes safely. Use when user asks to commit, push, or verify and push current changes.
  • 90commit-push
    Analyze changes, create categorized conventional commits, and push. Use when user asks to commit and push, invokes `/commit-push`, or requests conventional commits without a PR.
  • 91commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 98signal-push
    Stage all changes, create a conventional commit, then push to remote. One command for the full local→remote cycle. Use when user types /signal-push, "commit and push", "push everything", "push my changes", or wants to send current changes to remote without manual steps.
  • 100commit-push-pr
    Commit changes, push to remote, and create a pull request. Use for completing features or fixes ready for review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.