agentleFS
AurealibeAurealibe/claude-config/.claude/skills/commits/SKILL.md

commits

Skill68 starsChanged 4 months agoMITView on GitHub

Quick commit and push following Conventional Commits

  • Commits and pushes

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-tests and testing.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    writing-tests

    Use when adding or changing tests in Megatron-Energon, or when a code change needs test coverage. Covers the end-to-end test style, dataset fixtures, save/restore and multi-worker checks, and how to run focused tests.

    Also in 3 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Capitalize: after colon - fix: Add not fix: add

    line 31
  2. Very specific:

    Breaking changes: use ! - feat!: Remove deprecated API

    line 33
  3. Distinctive:

    Use when the change needs context

    line 39
  4. Distinctive:

    Use to specify the area affected:

    line 57
  5. Distinctive:

    Use to link commits to issues:

    line 99
  6. Distinctive:

    If no changes, exit silently

    line 108
  7. Distinctive:

    If push fails, report error only

    line 109

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

YOU ARE EXECUTING THE /commits SKILL. The user triggered this skill. Follow ALL instructions below step by step. Do NOT treat this as a freeform conversation - execute the skill workflow.

You are a git commit automation tool following Conventional Commits specification.

Workflow

  1. Stage: git add -A to stage all changes
  2. Analyze: git diff --cached --stat to see what changed
  3. Commit: Generate message following the format below
  4. Push: git push immediately

Message Format

<type>[optional scope]: <description>

[optional body]

Subject Line Rules

  • Max 50 characters - forces conciseness
  • Imperative mood - "Add" not "Added"
  • Capitalize after colon - fix: Add not fix: add
  • No period at the end
  • Breaking changes use ! - feat!: Remove deprecated API

Body Rules (optional, for complex changes)

  • Blank line after subject
  • Wrap at 72 characters
  • Explain why, not how
  • Use when the change needs context

Commit Types

TypeWhen to useSemVer
featNew featureMINOR
fixBug fixPATCH
docsDocumentation only-
styleFormatting, no logic change-
refactorCode change, no fix/feat-
perfPerformance improvement-
testAdding/updating tests-
buildBuild system, dependencies-
ciCI/CD configuration-
choreOther maintenance tasks-

Scope (optional)

Use to specify the area affected:

  • feat(auth): fix(api): docs(readme):

Examples

Simple (one line)

feat: Add user authentication
fix: Resolve memory leak in cache
docs: Update API documentation
refactor: Simplify validation logic

With scope

feat(auth): Add OAuth2 support
fix(api): Handle timeout errors gracefully
perf(db): Optimize query performance

Breaking change

feat!: Remove deprecated endpoints

With body (complex changes)

refactor(auth): Restructure token validation

Move token validation from middleware to dedicated service.
This improves testability and separates concerns between
request handling and authentication logic.

With issue reference (optional)

fix(auth): Resolve token expiration bug

Fixes #123

Footer Keywords (optional)

Use to link commits to issues:

  • Fixes #123 - closes the issue when merged
  • Closes #123 - same as Fixes
  • Refs #123 - references without closing

Execution

  • NO interactive commands
  • NO verbose output
  • If no changes, exit silently
  • If push fails, report error only

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.