Skip to content
TrustedSkillsbeta
Back to all skills

Naming Format

Checked
tartinerlabs·vlatest·utilities·MIT

Automatically generates consistent and compliant names/filenames based on provided rules and data structures.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add tartinerlabs/skills --skill naming-format -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

tartinerlabs

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned tartinerlabs/skills at a7812b928c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
a7812b928c
Manifest
plugins/quality/skills/naming-format/SKILL.md
Scanned
6 files, 277 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automatically analyzes a project's codebase to identify and correct naming inconsistencies, ensuring adherence to defined conventions. It scans for dominant casing patterns, framework indicators (like Next.js or Expo), existing suffix patterns, and export naming styles. The skill then audits files against pre-defined rules and offers automated fixes like renaming files using git mv and updating import paths.

When to use it

  • To enforce consistent naming conventions across a large codebase.
  • When onboarding new developers to ensure they follow project standards.
  • As part of an automated code review process to catch naming violations early.
  • To standardize file suffixes (e.g., .test.ts vs .spec.ts).
  • To improve the overall readability and maintainability of a project by adhering to framework conventions.

Key capabilities

  • Detects dominant filename casing conventions.
  • Identifies frameworks used in the project based on package.json.
  • Analyzes existing suffix patterns.
  • Audits code against rules for case consistency, file suffixes, export naming, and index files.
  • Reports violations grouped by severity (HIGH, MEDIUM).
  • Applies fixes including renaming files with git mv and updating import paths.

Example prompts

  • "Run a naming audit on the current project."
  • "Show me the high-severity naming violations."
  • "Apply fixes for all case consistency issues."
  • “What framework conventions are being used in this project?”

Tips & gotchas

  • The skill relies on individual rule files located in the rules/ directory, which contain detailed explanations and examples.
  • Review the audit results carefully before applying fixes to ensure accuracy.
  • The skill uses git mv for renaming, preserving git history; however, it's still recommended to review changes after automated fixes.