agentleFS
Sign inStart free
MalikZuMalikZu/frappe_agents/.claude/skills/semantic-commit/SKILL.md

semantic-commit

Skill0 starsChanged 3 months agoMITView on GitHub

Commit message format for this repo. Use every time you commit.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. aiatelie/ai-atelie★ 9same name
    2. agentconfig/agentconfig.org★ 7same name
    3. jonmagic/skills★ 6same name
    4. JailtonJunior94/skills★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    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:

    No plan text, no internal references, no issue-tracker prose.

    line 24
  2. Distinctive:

    No phase or plan labels (P0, P1, milestone names, spec names).

    line 25
  3. Very specific:

    Commit only what belongs in the open-source repo.

    line 28

“Common” is measured: kept by at least 6 in 10 of the 4 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

Semantic commits

Title: <type>: <what happened> — imperative, ≤ 72 chars. Types: feat fix docs chore refactor test ci perf.

Body: one bullet per thing done. Each bullet starts with a verb.

feat: add permission-checked document search tool

- add search_documents wrapping frappe.get_list
- filter results through the effective user's permissions
- log every call to Agent Tool Call

Rules:

  • Title says what happened. Bullets say what was done. Nothing else.
  • No plan text, no internal references, no issue-tracker prose.
  • No phase or plan labels (P0, P1, milestone names, spec names). The commit describes the code, not the plan that produced it.
  • No Co-Authored-By trailers.
  • Commit only what belongs in the open-source repo. internal/ never.
  • Stage files by name: git add <file> <file>. Never git add -A, git add ., or git add --all — you commit what you can list.

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