agentleFS
Sign inStart free
Agenta-AIAgenta-AI/agenta/.agents/skills/review-naming/SKILL.md

review-naming

Skill4.9k starsChanged 4 months agoLicence not identifiedView on GitHub

Review one code change, or one design (an OpenSpec change, a spec draft or an architecture doc), for naming, consistency and layering, and rate it Low, Medium, or High. Looks for one concept with several names across layers (table, column, DTO, route, JSON field, UI label), one word with two meanings, enum values from mixed schemes, names that mislead, item kinds or owner levels that break the shared resource pattern, singular and plural folder pairs, and layering faults such as pass-through layers, one decision in several places, rules that only one entry point checks, and doubtful public surface. Each finding cites the rule it breaks. Use when asked to "review the naming", "check this spec for consistent names", "is this PR consistent with our conventions", "review this PR that changes a contract", or when a review loop runs the naming lens. Read-only; it reports findings and does not fix them.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about Agenta-AI/agenta

The biggest 5 of 53 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 53

Talked about on GitHub and Bluesky (53 times).

On GitHub · 50

45 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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