agentsclimarketplace

Conventional commit

Skill jgamaraalv/delivery-loop/.claude/skills/conventional-commit

Continuous fullstack delivery loops — orchestrates frontend, backend, and quality subagents (behaviour drivers, engineers, UI/UX specialist, code/security reviewers, architects) in a test → diagnose → fix → review → secure → re-test cycle until the work is production-ready

Install
npx -y skills add jgamaraalv/delivery-loop --skill conventional-commit

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

One thing to look at

  • 0 stars0 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

Write and apply Conventional Commits — type(scope): subject, imperative mood, with body and BREAKING CHANGE footer when needed. Use when committing staged work or asked to write, review, or standardize a commit message.

SKILL.md

2.2 KB, 490 tokens by cl100k_base, as published. Nobody here has run it

Conventional Commit

Produce commit messages that follow the Conventional Commits specification: type(scope): description.

Workflow

  1. Run git status to review changed files.
  2. Run git diff (or git diff --cached) to inspect the changes — the message must describe what the diff actually does.
  3. Stage only the files that belong to this change: git add <file>.
  4. Construct the message with the structure below and commit: git commit -m "type(scope): description" (multi-line body/footer when needed).
  5. Stop there — never push, open, or merge a PR/MR; that is always a human action.

Message structure

type(scope): description

[optional body — the why and any context the diff doesn't show]

[optional footer — BREAKING CHANGE: details, or issue references]
  • type — one of feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert. Append ! for breaking changes (feat!:).
  • scope — optional but recommended: the module/area touched (e.g. auth, parser, ui).
  • description — required, short, imperative mood ("add", not "added"/"adds"), no trailing period.
  • body — optional; explain motivation and contrast with previous behavior.
  • footer — BREAKING CHANGE: <details> and/or issue references (Closes #123).

Examples

feat(parser): add ability to parse arrays
fix(ui): correct button alignment
docs: update README with usage instructions
refactor: improve performance of data processing
chore: update dependencies
feat!: send email on registration (BREAKING CHANGE: email service required)

Validation

Before committing, check: the type is in the allowed list, the description is imperative and matches the staged diff, breaking changes carry ! and a BREAKING CHANGE: footer, and the commit contains only the files of this one logical change (split unrelated changes into separate commits).

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 1 of the 12 instructions most pr commit review skills give in 490 tokens

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-07

  • Use conventional commits formatin 127 of 888, across 115 files
  • Keep subject line under 72 charactersin 62 of 888, across 48 files
  • Delete branches after mergein 51 of 888, across 38 files
  • Use imperative mood in subject linein 51 of 888, across 42 files
  • Use imperative mood in commit messagesin 44 of 888
  • Verify directory is ignored before creating worktreein 43 of 888, across 12 files
  • Generate a conventional commit messagein 43 of 888
  • Add unignored worktree directories to gitignorein 42 of 888, across 10 files
  • Make atomic commitsin 39 of 888, across 27 files
  • Run tests before committingin 36 of 888, across 25 files
  • Verify clean test baselinein 35 of 888, across 9 files
  • Split unrelated changes into separate commitshere, and in 35 of 888, across 30 files

Said here and by no other author read

  • start the message with type and scope

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

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.