naming-conventionslisted

Consistency gate that checks repository names against an agreed convention — file names, branch names, and Python/JS identifiers — using a simple, editable conventions.yml. Use when reviewing a PR, before committing, when creating new files or branches, or when the user asks whether names follow the team's standard. Keeps a growing codebase legible and machine-navigable.
abhinaykrupa/claude-skills · ★ 0 · Code & Development · score 65

Install: claude install-skill abhinaykrupa/claude-skills

# Naming-Conventions A lightweight standards gate so a fast-moving team (and its agents) keep names consistent — which matters a lot once multiple people and agents are all building. ## When to use - Reviewing a PR or a new module. - Before creating a new file or git branch. - When asked "does this follow our naming standard?" ## How to run it ```bash python check_naming.py <path> --config conventions.yml python check_naming.py --branch # check current git branch name ``` Exit `0` = compliant, `1` = violations found. ## How to respond to findings - Show each violation as `file/branch — rule — suggestion`. - Offer the corrected name; if the user agrees, rename (files via `git mv`). - If a rule is wrong for the team, edit `conventions.yml` — the standard should be living, not dogma. ## Convention (editable in conventions.yml) - **Files:** `kebab-case` for docs/config, `snake_case.py` for Python, `PascalCase` for React components. - **Branches:** `type/short-description` (e.g. `feat/idea-intake-agent`, `fix/secret-scan-fp`). - **Python:** `snake_case` functions/vars, `PascalCase` classes, `UPPER_SNAKE` constants. ## Install Drop into your Claude skills directory or a Claude Code plugin's `skills/`. Ship a repo-specific `conventions.yml` alongside it.