agentleFS
Sign inStart free
freemtyfreemty/labmate/skills/commit-changelog/SKILL.md

commit-changelog

Skill25 starsChanged 2 months agoMITView on GitHub

Use when preparing a focused git commit, updating a changelog, or committing nested repositories and their parent gitlinks. Triggers on "commit", "提交", "changelog", "weekly summary", "周报", "write commit message".

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update the changelog only when this repository treats it as part of the change contract.

    line 14
  2. Distinctive:

    Verify changed behavior, stage explicit paths, and review the staged diff.

    line 16
  3. Distinctive:

    Commit nested repositories first.

    line 17
  4. Very specific:

    Keep commit bodies about motivation, impact, and verification.

    line 21

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

Commit and Changelog

Turn the reviewed diff into the smallest coherent commit. Match the repository's existing style rather than imposing a universal template.

  1. Inspect status, diff, recent commits, and repository boundaries.
  2. Separate unrelated user changes. Never stage them for convenience.
  3. Update the changelog only when this repository treats it as part of the change contract.
  4. Verify changed behavior, stage explicit paths, and review the staged diff.
  5. Commit nested repositories first. Commit the parent only after the inner commit exists and the gitlink points to it.
  6. Push only when the user requested publishing.

Keep commit bodies about motivation, impact, and verification. Do not add a generic AI co-author trailer unless the project requires one. For weekly reporting, use the repository's weekly-report skill.

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