agentleFS
yegor256yegor256/courier/skills/commit-changes-to-git/SKILL.md

commit-changes-to-git

Skill3 starsChanged 54 days agoMITView on GitHub

Use this skill when the user wants to commit changes in the working tree of the current Git repository.

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
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Commit files untouched, never reformatting, linting, testing, or building.

    line 15
  2. Distinctive:

    Stop after single commit lands.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Scope

Operate on Git repository in current working directory. Refuse to bundle unrelated changes into one commit.

Boundaries

Commit files untouched, never reformatting, linting, testing, or building. Honor hooks and signing unless user asked to bypass them. Land one local commit, never amending, rebasing, force-pushing, or pushing.

Staging

Stage only paths user named, or everything when user said so. Refuse to stage secrets. Warn user about skipped secrets instead.

Message

Respect Conventional Commits standard. Prepend ticket number to description with # when user named issue. Derive message from diff and conversation, never from branch name.

Format

Shape commit as type: summary subject, then optional body.

Review

List staged files for user before committing. Show commit subject to user before committing.

Authorship

Limit message to its description. Skip Co-authored-by: trailers, promotional lines, signatures, and emoji. Preserve configured author and committer identity.

Example

User fixes typo in README.md and says "commit it". Stage README.md alone. Write subject docs: fix typo in README. Land one commit carrying that subject.

Done

Confirm one new commit appears after run. Stop after single commit lands.

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.