agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/git-craftsman/SKILL.md

git-craftsman

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Guides atomic commits, conventional commit formatting, clean branch strategies, and pull request walkthrough generation. Use when staging, committing, or preparing a PR.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Always review changes before staging:

    line 14
  2. Distinctive:

    When authoring a pull request summary, include:

    line 40

≈ “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

Git Craftsman

This skill enforces clean version control habits, atomic commits, and structured pull request walkthroughs.

Atomic Commit Workflow

1. Inspect Staged & Unstaged Diff

Always review changes before staging:

git status -s
git diff

2. Craft Conventional Commit Messages

Format commit messages strictly following the Conventional Commits specification:

<type>(<scope>): <short imperative summary>

[optional detailed body explaining WHY, not just WHAT]

[optional breaking changes or issue references]

Permitted Types:

  • feat: New feature or user-facing functionality.
  • fix: Bug fix.
  • refactor: Code change that neither fixes a bug nor adds a feature.
  • perf: Performance improvement.
  • test: Adding or correcting tests.
  • docs: Documentation only changes.
  • chore: Build system, configuration, or dependency updates.

3. Pull Request Walkthrough Format

When authoring a pull request summary, include:

  • High-Level Objective: What problem this PR solves.
  • Key Changes: Bulleted list of modified modules with clickable file links.
  • Verification Performed: Exact commands run (npm test, cargo test) and results.

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