agentsclimarketplace

Git commit

Skill MarcoAntolini/cursor-sync/cursor-skills/git-commit

Just a repo to sync my cursor skills, rules and commands.

Install
npx -y skills add MarcoAntolini/cursor-sync --skill git-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.
  • 1 stars1 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

Stages all changes and creates one Conventional Commits 1.0.0 commit. Does not push.

SKILL.md

1.6 KB, 372 tokens by cl100k_base, as published. Nobody here has run it

Git commit

One commit covering all current changes. Message grammar: Conventional Commits 1.0.0. Full header/body/footer rules → reference.md.

Steps

  1. Inspect with git status, git diff, and git diff --staged if anything is staged. Infer intent and any obvious breaking API/behavior change.
  2. Nothing to commit → say so and stop (no empty commit).
  3. git add -A, then re-check git diff --staged and git status --short so the message matches staged content only.
  4. Choose one type for the dominant change (feat for a new feature, fix for a bugfix, else docs / refactor / perf / test / build / ci / chore / style as fits).
  5. Write the message per reference.md. Prefer git commit -m "header" -m "body and footers" so the blank line after the header is preserved.
  6. Push only if this message explicitly asks.
  7. On success, paste the exact recorded message (git log -1 --format=%B) into chat — full header/body/footers, not a summary.
  8. Done when: one commit exists for the staged set, the chat shows that exact message, and you have not pushed unless asked — or you stopped with nothing to commit / awaiting split confirmation.

Split vs squash

Default is one commit. If the staged set clearly mixes unrelated work, warn and offer to split; split only on user confirm.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.