agentsclimarketplace

Commit hygiene

Skill felipeblassioli/agent-skills/skills/commit-hygiene

Commit hygiene and self-contained pull requests. Highlights production impact, uses gh CLI for opening/updating PRs, and adding proof comments (test runs, coverage reports).From its SKILL.md

Install
npx -y skills add felipeblassioli/agent-skills --skill commit-hygiene

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.
  • 2 stars2 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.

SKILL.md

1.7 KB, as published. Nobody here has run it

Commit Hygiene

Conventional Commits

Every commit message must follow Conventional Commits:

<type>(<optional scope>): <description>

[optional body]

Allowed types: feat, fix, refactor, perf, test, docs, chore, ci, build, style.

Separation of concerns per commit

Never mix these categories in a single commit:

CategoryFilesCommit type
Production code*.js in functions/ (excluding test*/, *.test.js, *.spec.js)feat, fix, refactor, perf
Test code*.test.js, *.spec.js, files under test*/ dirstest
Documentation*.md, docs/**, AGENTS.md, README*docs

Rules

  1. A commit touching production .js files must NOT include test or doc files.
  2. A commit touching test files must NOT include production .js or doc files.
  3. A docs-only commit must use docs: type and contain no code changes.
  4. Config/tooling files (Makefile, docker-compose.yaml, CI, .cursor/rules/) use chore or ci and may stand alone or accompany prod code if directly related.

Example sequence

feat(scoring): add cooldown window to scoring
test(scoring): add unit tests for cooldown scoring
docs: document cooldown scoring behavior

When in doubt

If a change requires both prod and test updates (e.g., TDD), create two commits: one for the production code, one for the tests. Mention the relationship in the commit body if helpful.

Keep looking

Skills are one crate of 609,689. 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.