code-quality

Identify code-quality issues and propose concrete refactoring steps with severity levels.

6|2|Updated Jul 8, 2012
One-click install
npx skills add https://github.com/athal7/dotfiles --skill code-quality-athal7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/athal7/dotfiles/tree/main/skills/code-quality
Command: npx skills add https://github.com/athal7/dotfiles --skill code-quality-athal7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides reference content for naming and addressing structural and hygiene problems in code. Consumers cite the relevant pattern or rule by name, helping teams align on refactoring direction and severity.

Core Features & Use Cases

  • Reference patterns for common code-quality issues (e.g., Feature Envy, Premature Abstraction) with guidance on when to apply them.
  • Help reviewers name, evaluate, and propose concrete refactoring steps and severity levels during code reviews.
  • Useful during design discussions to keep code maintainable and aligned with standards.

Quick Start

Review a diff and cite applicable patterns from this catalog to guide a safe refactor.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I identify code smells like Feature Envy and Primitive Obsession during a code review?

Code smells like Feature Envy and Primitive Obsession are identified by mapping code changes to recognized structural patterns, evaluating severity, and proposing explicit refactoring directions to extract policy objects or rename patterns.

What is the best way to guide concrete refactors when changes touch multiple modules?

The best way to guide concrete refactors across multiple modules is to cite established code-quality patterns by name, assign severity levels, and apply guardrails to ensure safe structural changes and maintainable design.

When do I need to extract policy objects or apply anti-pattern fixes in architecture discussions?

You need to extract policy objects or apply anti-pattern fixes when evaluating structural changes that touch multiple modules, helping teams align on refactoring direction and maintain code hygiene during design discussions.

Can I use static analysis patterns to name and evaluate structural code-quality issues?

Yes, static analysis patterns can be used to name and evaluate structural code-quality issues by referencing established rules, allowing reviewers to propose concrete refactoring steps and align on severity levels.

How do I address premature abstraction and shotgun surgery when reviewing a diff?

Address premature abstraction and shotgun surgery by citing applicable code-quality patterns from a reference catalog, evaluating the structural impact, and guiding a safe refactor with explicit guardrails and severity levels.