agentleFS
Sign inStart free
hanyang-techhanyang-tech/claude-skills/skills/conventions/SKILL.md

conventions

Skill0 starsChanged 15 days agoNo licenceView on GitHub

Work out how a codebase is actually written and record it as a short, evidence-backed conventions doc that people and other skills can follow. Samples the codebase's most established files, extracts conventions across layout, naming, errors, validation, types, logging, config, data access, boundaries, concurrency, dependencies, comments, tests, library choices and git style, then counts how widely each one holds across the whole codebase and marks it established, prevailing or mixed, with exemplars and counter-examples. Asks the user to settle mixed areas and migrations, writes docs/conventions.md with a reuse index of the helpers to use, points CLAUDE.md at it, and proposes lint rules for what a tool can check. Use when the user asks to document, extract, learn or write down a codebase's conventions, style guide, coding standards or house style, wants a CLAUDE.md or conventions file for a repo, or invokes /conventions (options --out, --scope, --update, --auto, --models). Commits nothing.

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use review and release.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    review

    Fixture review skill.

    Also in 3 projects that use this

  • MicrosoftSkill

    release

    Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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