agentleFS
Sign inStart free
ProjectWajaProjectWaja/claude-skillcraft/skills/clean-commit/SKILL.md

clean-commit

Skill0 starsChanged 6 months agoMITView on GitHub

Enforces atomic commits, conventional commit messages, and clean PR and git history. Use when committing, staging changes, or opening a PR.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every commit tells a story.

    line 14
  2. Distinctive:

    If you can't describe the commit in one sentence, it's too big — split it

    line 41
  3. Distinctive:

    Remove debug logging, console.logs, and commented experiments

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Clean Commit

Every commit tells a story. Every PR has context. No exceptions.

Commit Rules

Message Format

Follow Conventional Commits:

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

[optional body]

[optional footer]

Types: feat, fix, refactor, test, docs, chore, perf, ci

Rules:

  • Subject line under 72 characters
  • Imperative mood ("add feature" not "added feature")
  • Body explains why, not what (the diff shows what)
  • Reference issue numbers in the footer when applicable

Atomic Commits

  • One logical change per commit
  • If you can't describe the commit in one sentence, it's too big — split it
  • Tests and implementation go in the same commit (they're one logical change)
  • Config changes, dependency updates, and code changes are separate commits

What Not to Commit

  • .env files or any secrets
  • Build artifacts, node_modules, __pycache__
  • IDE-specific config (.vscode/, .idea/) unless project-shared
  • Large binaries without LFS

PR Rules

Title

  • Under 70 characters
  • Same format as commit subject: type(scope): description

Description

Every PR includes:

  1. Summary — 1-3 bullet points on what and why
  2. Test plan — How to verify this works
  3. Screenshots — If UI changed, before and after

Before Opening

  • Rebase on latest target branch
  • All tests pass
  • Self-review the full diff one more time
  • Remove debug logging, console.logs, and commented experiments

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.

Check your setup, free