coding-standards

Enforces baseline coding conventions for naming, immutability, readability, and code-quality review.

Updated Jul 22, 2026
One-click install
npx skills add https://github.com/Chau165/local_skill --skill coding-standards-chau165
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/Chau165/local_skill/tree/main/plugins/ecc/skills/coding-standards
Command: npx skills add https://github.com/Chau165/local_skill --skill coding-standards-chau165

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent naming, mutation bugs, missing error handling, and unclear structure slow down code reviews and create maintenance debt across projects. This Skill provides a shared baseline of coding conventions so every module follows the same quality floor. ## Core Features & Use Cases - Naming and Readability Rules: Enforces descriptive variable and function names, verb-noun function patterns, and self-documenting code over comments. - Immutability and Type Safety: Mandates spread-operator updates, typed interfaces, and avoidance of any in TypeScript/JavaScript code. - Code Smell Detection: Flags long functions, deep nesting, and magic numbers with concrete refactoring patterns like early returns and named constants. - Use Case: When reviewing a pull request that mutates state directly and uses unclear variable names, apply this Skill to rewrite the code with immutable updates, descriptive naming, and proper error handling. ## Quick Start Review this TypeScript module against the baseline coding standards and refactor any naming, immutability, or error-handling violations.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I enforce consistent coding standards across a project?

Apply a shared baseline covering descriptive naming, immutability with spread operators, and comprehensive error handling. Use this Skill during code reviews and refactoring, then delegate framework-specific patterns to dedicated frontend or backend skills.

How to avoid state mutation bugs in TypeScript and React?

Always use the spread operator for updates, such as `{...user, name: 'New Name'}` or `[...items, newItem]`, instead of direct mutation like `items.push()`. For React state, use functional updates like `setCount(prev => prev + 1)` to avoid stale values.

When should I use this skill instead of framework-specific guidelines?

Use it for cross-cutting concerns like naming, immutability, error handling, and code-smell review. For React hooks, rendering patterns, backend architecture, or API layering, switch to the dedicated frontend-patterns, backend-patterns, or api-design skills.

What code smells should I look for during code review?

Watch for functions longer than 50 lines, nesting deeper than a few levels, and unexplained magic numbers. Fix them by splitting logic into smaller functions, using early returns to flatten conditionals, and replacing literals with named constants.

Does this skill replace linting and formatting tools?

No, it complements them. Linters automate formatting and syntax rules, while this Skill guides judgment-based decisions like naming clarity, when to comment, error-handling depth, and structural refactoring that automated tools cannot evaluate.