Skip to main content

Software Development

Naming Convention Audit

Naming Convention Audit turns code quality & refactoring material into a review report with a concrete naming code smell classification, convention refactor sequencing plan, and audit test and blast-radius guardrail. It is built for teams that need a usable draft artifact, not a broad summary with a familiar title. The skill asks for code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context up front, then organizes the output around naming, convention, audit, code, and quality. It is delivered with adapters for Claude Code, Codex, OpenClaw, and Antigravity so teams can use the same workflow across their preferred agent environment. Naming Convention Audit is scoped to the Code Quality & Refactoring workflow and is distinct from adjacent catalog skills by producing this specific deliverable rather than a broad summary.

Nexus CertifiedClaude CodeCodexOpenClawGoogle Antigravity
namingconventionauditcodequality

One-Time Purchase

$19.99

Sample Output

Naming Convention Audit — Sample Brief

Headline

Builds a code-quality repair plan for naming convention audit work, turning code excerpts, dependency map, or static-analysis notes, complexity, duplication, or naming concerns, and risk tolerance and test coverage context into naming code smell classification, convention refactor sequencing plan, and audit test and blast-radius guardrail. In this example, target repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun. The output is a concrete review report: source evidence, reviewer checks, and the owner decision that determines whether the work is ready.

Evidence Packet

InputExampleStatus
code excerpts, dependency map, or static-analysis notestarget repository module needs a repository-backed review with commands, files, and acceptance tests that engineering can rerun.Provided
complexity, duplication, or naming concernsThree representative examples from the current workflowReviewed
risk tolerance and test coverage contextApproval threshold and final reviewerConfirm
desired refactor size and review pathCode Quality & Refactoring owner and downstream audienceReady

Naming Evidence Model

FieldWhat must be capturedReview consequence
Naming signalAnchor the result in naming, convention, and audit evidence from the supplied material.Treat as draft until naming code smell classification is source-backed.
Naming Code Smell ClassificationSeparate Naming signal, Convention judgment, and Audit action before drafting.Escalate when naming evidence is missing or contradicted.
Convention Refactor Sequencing PlanName the review question that makes Naming Convention Audit different from the rest of Code Quality & Refactoring.Reviewer resolves audit test and blast-radius guardrail before final use.

Naming Acceptance Checks

CheckRequired evidenceReview action
Naming depthAnchor the result in naming, convention, and audit evidence from the supplied material.Keep, revise, or ask a targeted follow-up
Convention boundarySeparate Naming signal, Convention judgment, and Audit action before drafting.Confirm this is not a renamed adjacent bundle skill
Audit handoffName the review question that makes Naming Convention Audit different from the rest of Code Quality & Refactoring.Assign the owner decision before final use

Naming Convention Audit Work Map

Naming Convention Audit focus areas

Extract the details that determine whether the review report is useful.naming code smell classification
Separate draftable material from items that need reviewer judgment.convention refactor sequencing plan
Package the result so the next owner sees the exact edit or approval needed.audit test and blast-radius guardrail

Draft Review Report

Naming signalNaming Code Smell ClassificationConvention Refactor Sequencing PlanAudit Test And Blast Radius GuardrailConvention decision
Namingnaming code smell classificationconvention refactor sequencing planaudit test and blast-radius guardrailKeep if source-backed
Conventionnaming code smell classificationconvention refactor sequencing planNaming evidence is missing or contradicted.Revise missing evidence
AuditAnchor the result in naming, convention, and audit evidence from the supplied material.Separate Naming signal, Convention judgment, and Audit action before drafting.audit test and blast-radius guardrailAssign owner decision

Use now

Naming Convention Audit

Best when code quality & refactoring work needs a concrete review report.

Keeps the artifact tied to supplied materialNaming
Names the next edit, approval, or owner decisionConvention

Hold back

Missing evidence

Best deferred when a key input would change the artifact.

Naming evidence is missing or contradicted.Naming
Convention constraints would change the recommendation.Convention
The reviewer cannot tell how Naming Convention Audit differs from adjacent Code Quality & Refactoring work.Audit

Reviewer note

The output is structured so an operator can validate the draft, edit the artifact, and hand it to the next owner without re-reading the entire packet. The final answer should label unknowns plainly and avoid inventing metrics, policies, quotes, or commitments.

This sample illustrates the skill's output format. The artifact reviewed is illustrative and should be validated against the real repository before implementation.

View full sample →

All sales final. No refunds on digital products.

Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.

Also in Code Quality & Refactoring

Bundle price: $44. Compare this skill with the full workflow bundle or Pro access.

Best for

Engineers auditing naming consistency across a codebase — classifying the smells and sequencing low-risk renames. Most useful before onboarding new engineers or after a merge of two codebases left inconsistent conventions everywhere.

Not ideal for

Tiny or solo codebases where consistency is not a problem yet, and behavior-changing refactors. It flags the names — an engineer confirms each rename is safe and worth the churn before applying it.

Included in this purchase

  • Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
  • Setup guidance for the right adapter in your workspace.
  • One-time license for the purchased skill version.

Setup

Plan for a short setup in the repository or workspace where the skill will run. Some coding familiarity helps for implementation-heavy outputs.

Claude CodeCodexOpenClawGoogle Antigravity

Related Skills

Code Generation & Review
Featured
Code Generation
Generates, reviews, debugs, and executes code in sandboxed workflows. Useful for implementation, refactoring, and technical problem solving.
Claude CodeCodexOpenClawGoogle Antigravity
codingdebuggingcode-review

$19.99

One-time license

View Skill
Product Documentation & Onboarding
API Documentation Generator
Generates structured, developer-ready API documentation from code, OpenAPI specs, route definitions, or descriptions. Produces reference docs, quickstart guides, error references, and code examples.
Claude CodeCodexOpenClawGoogle Antigravity
apidocumentationdeveloper-experience

$19.99

One-time license

View Skill
Code Generation & Review
Intelligent PR Composer
Generates pull request descriptions that capture context, alternatives considered, test plan, risk areas, and reviewer guidance beyond a simple diff summary. Useful for teams that want senior-quality PRs without manual authoring.
Claude CodeCodexOpenClawGoogle Antigravity
pull-requestscode-reviewgit

$19.99

One-time license

View Skill

Future Updates

This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.

Upgrade to Pro