code-style-rules

Enforce consistent code style and naming conventions during code review and refactoring.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zcawood-mie/agentz --skill code-style-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-style-rules
Source: https://github.com/zcawood-mie/agentz/tree/main/skills/code-style-rules
Command: npx skills add https://github.com/zcawood-mie/agentz --skill code-style-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent and ambiguous identifiers, poor commenting, and ad-hoc naming conventions cause confusion, bugs, and technical debt across codebases; these rules provide a shared standard to reduce cognitive load and make code easier to read and maintain.

Core Features & Use Cases

  • Variable and Identifier Rules: Lists forbidden short names and abbreviations and offers clear, descriptive alternatives for variables, parameters, and return values.
  • Loop and Index Naming: Prescribes meaningful loop index names that reflect the iterated data to avoid confusion in nested loops.
  • Comment and Function Guidance: Specifies which comments to remove versus keep, recommends action-oriented function names, and encourages single-responsibility functions to aid refactoring and reviews.
  • Use Case: Apply these rules during code review or automated refactoring to rename unclear variables, remove stale comments, and standardize function names across modules.

Quick Start

Ask the agent to refactor the provided code to follow code-style-rules by renaming ambiguous variables, removing stale comments, and suggesting clearer function names.

Frequently Asked Questions about code-style-rules

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

FAQPage Schema
How do I enforce consistent code style and naming conventions during a code review?

To enforce consistent code style during code review, apply rules to variable naming, forbidden abbreviations, loop index names, comment hygiene, and function naming to eliminate ambiguous identifiers and reduce cognitive load.

What are the best practices for renaming ambiguous variables and identifiers in source code?

Best practices for renaming ambiguous variables involve replacing forbidden short names and abbreviations with clear, descriptive alternatives for variables, parameters, and return values to improve readability and maintainability.

How do I clean up stale comments and standardize function names when refactoring?

To clean up comments and standardize function names during refactoring, remove stale comments while retaining necessary ones, and rename functions to be action-oriented with single-responsibility to aid code reviews.

When do I need to apply specific naming patterns for loop index names in nested loops?

You need specific naming patterns for loop index names in nested loops to avoid confusion, prescribing meaningful loop index names that reflect the iterated data and ensure clear code style across modules.

Does automated style checking work for providing explicit replacement suggestions for unclear identifiers?

Automated style checking works by applying rules to provide explicit replacement suggestions and contextual naming patterns for unclear identifiers, improving source code readability during refactoring.

Why does inconsistent code style cause confusion and technical debt in codebases?

Inconsistent code style causes confusion and technical debt because ambiguous identifiers and ad-hoc naming conventions increase cognitive load, making source code harder to read and maintain without a shared standard.