skills.rest
NoxelS
NoxelSCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

coding-standards

Identify code smells and anti-patterns in codebases during reviews and refactors.

2|Updated Feb 16, 2026
Search Tags:#anti-patterns#refactoring#readability#coding#static-analysis#code-smells
One-click install
npx skills add https://github.com/NoxelS/agentic-uv --skill coding-standards-noxels
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/NoxelS/agentic-uv/tree/main/.copilot/skills/coding-standards
Command: npx skills add https://github.com/NoxelS/agentic-uv --skill coding-standards-noxels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coding teams often accumulate technical debt through anti-patterns and unreadable code, slowing development and increasing bug risk. This Skill identifies and helps address code smells, ensuring consistent quality and maintainability.

Core Features & Use Cases

  • Detects common code smells and anti-patterns in reviews and during refactoring.
  • Provides guidance for improving readability and maintainability of codebases.
  • Use case: during feature implementation, code review, or large refactoring, run checks to surface design violations and suggested improvements.

Quick Start

Use this skill to audit a codebase for smells and refactor opportunities.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I identify code smells and anti-patterns during a code review?▼

Refactoring code smells improves readability and maintainability by applying a structured rule set of anti-patterns and readability heuristics. This process surfaces architectural debt and maintenance risks, yielding actionable recommendations to update the codebase.

What are common anti-patterns that reduce codebase readability and maintainability?▼

Common anti-patterns that reduce readability include structural designs violating predefined heuristics, leading to technical debt and increased bug risk. Identifying these code smells requires checking the codebase against a structured rule set during feature development or refactoring.

How do I audit a codebase for technical debt and refactoring opportunities?▼

Audit a codebase for technical debt by running checks for code smells and anti-patterns during large-scale refactors. This evaluates the code against readability heuristics to surface architectural debt and output actionable recommendations for code improvement.

Does static analysis help surface architectural debt during feature development?▼

Static analysis helps surface architectural debt during feature development by applying readability heuristics and a structured rule set for anti-patterns. This identifies code smells early, ensuring consistent quality and reducing maintenance risks before deployment.

When should I run checks for code smells in my software engineering workflow?▼

Run checks for code smells during feature implementation, code reviews, and large-scale refactors. Applying readability heuristics and anti-pattern rules at these stages surfaces design violations and maintenance risks, directly addressing accumulated technical debt.

Related Skills

Explore More Software Engineering Skills→
uukuguyuukuguy
1

code-metrics

Calculate complexity, size, coupling, and duplication metrics from source code.

Community
Intermediate
ngquaanghuyngquaanghuy

ponytail-audit

Analyze entire codebases to identify and rank over-engineering issues.

Community
Intermediate
AsiaOstrichAsiaOstrich
70

discover

Assess project health, architecture, and risks in existing codebases.

Community
Intermediate
ImaginerLabsImaginerLabs

quality-analyst

Assess code quality and quantify technical debt across a codebase.

Official
Intermediate