skills.rest
MARUCIE
MARUCIECOMMUNITY
Explore all skills by this author →
GitHub

coding-standards

Reviews code against naming conventions, SOLID principles, design patterns, and code smell catalogs.

1|Updated Mar 18, 2026
Search Tags:#code review#refactoring#design patterns#coding standards#code smells#naming conventions#solid principles
One-click install
npx skills add https://github.com/MARUCIE/openclaw-foundry --skill coding-standards-marucie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/MARUCIE/openclaw-foundry/tree/main/web/public/packs/spellbook-code-reviewer/skills/coding-standards
Command: npx skills add https://github.com/MARUCIE/openclaw-foundry --skill coding-standards-marucie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often stall on style debates, inconsistent naming, and recurring design mistakes. This Skill provides a single baseline covering naming conventions, SOLID principles, design patterns, and code smells across Python, TypeScript, and Go, so reviewers focus on design decisions instead of style arguments. ## Core Features & Use Cases - Naming and Style Baseline: Language-specific tables for variables, functions, classes, constants, and files in Python, TypeScript, and Go, plus heuristics for boolean prefixes and verb-phrase function names. - SOLID and Design Pattern Reference: Annotated good/bad code examples for all five SOLID principles and twelve common patterns including Factory, Strategy, Observer, and Repository. - Code Smell Catalog: A symptom-to-refactoring mapping for ten common smells such as God Class, Primitive Obsession, and Magic Numbers, with a red-flag list and review checklist. - Use Case: During a pull request review, activate this Skill to check whether a new TypeScript service violates dependency inversion, contains magic numbers, or uses any at module boundaries, then cite the specific convention in review comments. ## Quick Start Review this pull request against the coding standards and flag any naming violations, SOLID principle breaches, or code smells with suggested refactorings.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I review code for SOLID principle violations?▼

Check each class for a single responsibility, verify subtypes are substitutable for base types, and confirm dependencies are injected against interfaces rather than instantiated concretely. The Skill provides good and bad TypeScript examples for all five principles to compare against.

What naming conventions should I use in Python, TypeScript, and Go?▼

Python uses snake_case for variables and functions with PascalCase classes, TypeScript uses camelCase with PascalCase types, and Go uses PascalCase for exported and camelCase for unexported identifiers. Booleans should use is_, has_, or can_ prefixes and functions should be verb phrases.

When should I avoid using a design pattern like Singleton or Factory?▼

Avoid Singleton when it becomes global mutable state, Factory when only one type exists, and Builder for simple objects with few fields. Patterns should only be applied where they genuinely simplify the code, not by default.

What are common code smells and how do I fix them?▼

Common smells include Long Method (fix with Extract Method), Primitive Obsession (introduce Value Objects), Magic Numbers (replace with named constants), and God Classes (split via Extract Class). Each smell maps to a specific refactoring technique.

Why are mutable default arguments dangerous in Python?▼

A default like def process(items=[]) shares one list across all calls, causing state to leak between invocations. Use def process(items=None) and initialize the list inside the function body instead.

Related Skills

Explore More Software Engineering Skills→
EpiphyticEpiphytic
7

code-review

Review source code changes for quality issues and improvement opportunities.

Official
Basic
kirvinkirvin

commit

Stage Git changes and create conventional commit messages with preflight checks.

Community
Intermediate
KimjimanKimjiman

springboot-verification

Automate build, static analysis, tests, security scans, and diff review for Spring Boot projects.

Community
Advanced
georgekhananaevgeorgekhananaev
27

code-quality

Enforce cross-language code quality standards across TypeScript, Python, Go, and Rust.

Community
Advanced