Agent Skills: review-naming
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.
Install this agent skill to your local
Skill Files
The files that make up review-naming.
Loading file tree…
More agent skills
- triage-findingsCoordinate findings work with the user, decide whether scan, test, or sync should run, and turn the current findings set into a ready plan. Accept optional `path` and GitHub PR `url`; default to `path=infer`. Confirm effective variables before starting.
- resolve-findingsResolve findings by implementing the chosen fix path in code, tests, or docs. Accept optional `path` and a `priority` selector; by default resolve only the next highest remaining priority bucket, in order `P0`, `P1`, `P2`, `P3`. Also accept explicit levels or `all`. Default to `path=infer`. Confirm effective variables before starting.
- create-changelog-announcementUse this skill to create and publish changelog announcements for new features, improvements, or bug fixes. This skill handles the complete workflow - creating detailed changelog documentation pages, regenerating the in-app What's New data, and ensuring everything follows project standards. Use when the user mentions adding changelog entries, documenting new features, creating release notes, or announcing product updates.
- update-api-docsUpdate the API reference documentation by downloading the latest OpenAPI spec from production and regenerating the Docusaurus API docs
- write-docsUse when writing or editing documentation pages (concept pages, how-to guides, API reference prose, tutorials) under docs/. Provides the writing style, voice, and structural rules for Agenta docs. Apply this skill before drafting any new docs page, and include it in the brief for any subagent tasked with writing docs.
- test-codebaseRun or inspect the relevant validation paths and turn failures, regressions, or missing coverage into findings. Accept optional `path` and `depth` parameters and default to `path=infer`, `depth=deep`. Confirm effective variables before starting.