Skip to content
Skills Library
Programming · Building & coding

committing

/committing

Makes clean git commits in the project's own style. Use when the user asks to commit, write a commit message, split changes into commits, or open a PR. Not for reviews or explaining history.

Repository
foma-skills ↗
Licence
Apache-2.0
Last repository change
13.11.2026

Assessment and security

90/ 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.
Content25 / 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
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

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

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Makes clean git commits in the project's own style. Use when the user asks to commit, write a commit message, split changes into commits, or open a PR. Not for reviews or explaining history.

Original author description

Makes clean git commits in the project's own style. Use when the user asks to commit, write a commit message, split changes into commits, or open a PR. Not for reviews or explaining history.

How it works

  1. Steps
  2. Rules
  3. Report
Original SKILL.md headings · 28 lines, 377 words
SKILL.md preview
---
name: committing
description: >-
  Makes clean git commits in the project's own style. Use when the user asks to commit, write a commit message, split changes into commits, or open a PR. Not for reviews or explaining history.
license: Apache-2.0
metadata:
  level: "atomic"
  uses: ""
  agents: ""
  tokens: "556"
---

Commit only your own finished changes, in small focused commits, in the message style the project already uses.

Path: one obvious change → steps 1, 3, 5 and one commit, no ceremony; mixed changes → propose a split first. Say which path in one line.

## Steps
1. Run `git status` and `git diff` (staged and unstaged). Separate what you changed for this task from other changes in the tree.
2. Mixed or unrelated changes: propose the split (one logical change per commit, with file lists and messages) and wait for the user's ok.
3. Find the message style: the project's CLAUDE.md first (Workflow, Conventions, git section), else `git log --oneline -10`. Match language, tense, prefix and length. Add a trailer (Co-Authored-By etc.) only if the project's rules or the session's attribution instructions call for one.
4. Check the files to stage for secrets (`.env`, keys, tokens, credentials) and junk (build output, logs, scratch files, debug lines). Leave them out and tell the user.
5. Stage by path (`git add <path>…`). Run `git diff --cached -U0 | grep -n '^+.*\[DEBUG-'`; a hit is a temporary debug line you are about to commit (foma-skills:debugging tags them): remove it, restage, then commit. Removed lines do not count.
6. Commit now only if the user asked to commit or the project's CLAUDE.md says to commit after each finished task. Otherwise show the proposed message and staged files and ask first.
7. Run `git status` to confirm what was committed and what remains.

## Rules
- Never `git add -A`, `git add .` or `git commit -a`; they pick up files you did not change.
- Never push without an explicit ask in this conversation; a past ask does not carry over.
- Never amend, rebase, force-push, `reset --hard`, `clean -f`, `branch -D`, `checkout .` / `restore .`, or skip hooks (`--no-verify`) without an explicit ask for that exact action.
- A failing hook is fixed, not bypassed; make a new commit rather than amending.
- One logical change per commit; never mix refactor, feature and formatting.

If the user asks to open a PR, read `references/pull-request.md`.

## Report
- Commit hash(es) and message(s), or the proposed message awaiting ok.
- Left uncommitted, if anything, and why.
- Not checked: <…>
Files in this package (2)
  • SKILL.md 2 KB
  • references/pull-request.md 1 KB

Versions

The database has no other skills named committing.

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

Downloads in the last 30 days: 1 · ranking

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

Similar skills

  • 100git-commit
    Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs…
  • 100commit-work
    Create high-quality git commits: review/stage intended changes, split into logical commits, write clear Conventional Commits messages, and run the project's pipeline gate before each commit. Use when committing within an rem-sdlc cycle or whenever staging changes.
  • 100git-commit
    Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs…
  • 90commit-work
    Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
  • 100writing-git-commits
    Split staged or uncommitted changes into conventional commits. Use when asked to commit, generate commit messages, split commits, squash commits, or reorder history.
  • 100commit
    Create focused git commits from current working tree changes. Use when the user asks to commit changes, make a git commit, write a commit message, split changes into commits, organize commits, group changes into commits, or prepare local changes for commit.

Feedback and reports

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