skills.rest
BrunoAMSilva
BrunoAMSilvaCOMMUNITY
Explore all skills by this author →
GitHub

code-conventions

Enforce naming, file structure, and code organization policies across projects.

Updated Apr 14, 2026
Search Tags:#conventions#best-practices#code-review#naming#dead-code#code-structure#single-responsibility
One-click install
npx skills add https://github.com/BrunoAMSilva/my-config --skill code-conventions-brunoamsilva
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-conventions
Source: https://github.com/BrunoAMSilva/my-config/tree/main/coding/skills/code-conventions
Command: npx skills add https://github.com/BrunoAMSilva/my-config --skill code-conventions-brunoamsilva

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent naming, scattered responsibilities, dead code, and variable shadowing make codebases hard to read, maintain, and safely extend across languages and frameworks. This Skill provides concise, language-agnostic rules to restore clarity, reduce bugs, and make code reviews and onboarding faster.

Core Features & Use Cases

  • Consistent Naming Rules: Enforce camelCase for variables and functions, PascalCase for classes/components, and UPPER_SNAKE_CASE for constants.
  • Single Responsibility per File: Ensure each file has one clear responsibility and its name matches the primary export or role.
  • No Dead Code & No Shadowing: Remove unused imports/variables/commented-out code and avoid inner-scope names that shadow outer scope identifiers.
  • Decision Tree & References: Provide a decision tree for when to apply universal rules versus technology-specific skills and link to detailed reference docs for naming, imports, structure, and documentation standards.
  • Use Cases: Establish cross-project standards, perform pre-merge code reviews, and audit legacy modules for maintainability improvements.

Quick Start

Ask the assistant to review a module for naming consistency, single-responsibility violations, dead code, and variable shadowing and provide prioritized, actionable fixes.

Frequently Asked Questions about code-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent naming conventions and code structure across different programming languages?▼

To enforce consistent naming conventions across languages, apply universal rules like camelCase for variables, PascalCase for classes, and UPPER_SNAKE_CASE for constants. This ensures codebase clarity and reduces bugs during code reviews and onboarding.

What is the best way to check for dead code and variable shadowing during a pre-merge code review?▼

Checking for dead code and variable shadowing during a code review involves scanning for unused imports, commented-out code, and inner-scope variables hiding outer identifiers. This process restores maintainability and prevents unexpected runtime scope bugs.

How do I audit legacy modules for single responsibility and file structure violations?▼

Auditing legacy modules for single responsibility involves verifying each file has one clear role and its name matches the primary export. This structural cleanup makes older codebases safer to extend and easier to navigate.

Can I apply universal code organization standards to any framework or tech stack?▼

You can apply universal code organization standards to any framework or tech stack when defining naming, file responsibilities, and dead code elimination. A decision tree helps determine when to apply these universal rules versus technology-specific guidelines.

Why does variable shadowing cause bugs and how can I eliminate it from my codebase?▼

Variable shadowing causes bugs by allowing inner-scope identifiers to hide outer-scope variables, leading to unexpected behavior. You can eliminate it by enforcing strict naming policies that avoid reusing identifiers across nested scopes during code reviews.

Related Skills

Explore More Software Engineering Skills→
civictechdccivictechdc
1

python-project-structure

Plans Python project structure and module architecture with explicit __all__ exports.

Official
Intermediate
adolfoaranaes12adolfoaranaes12
2

execute-task

Execute approved task specifications sequentially with TDD and validation gates.

Community
Advanced
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced
canonicalcanonical
29

documentation-style

Validate documentation against style guides and MyST/reST syntax.

Official
Intermediate