agentsclimarketplace

Conventional commits

Skill LichAmnesia/awesome-antigravity-skills/skills/conventional-commits

A curated list of awesome Agent Skills, skill collections, and resources for Google Antigravity — the agent-first IDE powered by Gemini 3

Install
npx -y skills add LichAmnesia/awesome-antigravity-skills --skill conventional-commits

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

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 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

Writes git commit messages following the Conventional Commits 1.0.0 spec. Use when committing changes, when the user asks for a commit message, or when a repo enforces commit linting.

SKILL.md

1.9 KB, as published. Nobody here has run it

Conventional Commits

When creating a commit message, follow Conventional Commits 1.0.0.

When to use this skill

  • The user asks to commit staged or unstaged changes.
  • The user asks "write a commit message for this diff".
  • The repo has commitlint, husky, or a CONTRIBUTING.md mentioning Conventional Commits.

How to use it

  1. Inspect the change first: git diff --staged (or git diff if nothing is staged). Never invent a message without reading the diff.
  2. Pick the type from the actual change, not the file names:
    • feat — user-visible behavior added
    • fix — user-visible bug fixed
    • refactor — behavior-preserving restructure
    • docs, test, build, ci, chore, style, perf
  3. Add a scope when the repo already uses them (check git log --oneline -20 for the house style).
  4. Subject line: imperative mood, lowercase after the colon, no trailing period, ≤ 72 chars.
  5. Body (optional): explain why, wrap at 72. Footer: BREAKING CHANGE: or issue refs (Closes #123).

Decision tree

  • Mixed unrelated changes in one diff → propose splitting into multiple commits instead of one vague chore.
  • Change is a revert → use revert: and reference the reverted SHA.
  • Unsure between fix and refactor → does an end user observe the difference? Yes = fix, no = refactor.

Done means

git log -1 --format=%s matches ^(feat|fix|refactor|docs|test|build|ci|chore|style|perf|revert)(\(.+\))?!?: .+ and the message honestly describes the diff.

Part of awesome-antigravity-skills. Browse more Agent Skills at orangebot.ai/skills.

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.