guru-smells

Name: guru-smells
Availability: InStock
Author: cyblow

Identify code smells and prescribe targeted refactoring patterns for object-oriented codebases.

1|Updated Dec 22, 2025

Search Tags:#refactoring #code-quality #best-practices #software-engineering #design-patterns #code-smells

Ready to run

npx skills add https://github.com/CybLow/pypaginate --skill guru-smells

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guru-smells
Source: https://github.com/CybLow/pypaginate/tree/main/.opencode/skills/guru-smells
Command: npx skills add https://github.com/CybLow/pypaginate --skill guru-smells

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, actionable catalog of code smells—detailing symptoms, causes, and remediation strategies to help teams identify and fix maintainability issues early in a codebase.

Core Features & Use Cases

Comprehensive catalog of code smells across categories (Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers).
For each smell, presents symptoms, causes, and recommended refactoring treatments with concrete examples.
Practical use in code reviews, onboarding, and architectural planning to improve code quality and consistency.

Quick Start

Review the guru-smells guidelines and apply the categorized refactoring patterns to improve code quality in your project.

Frequently Asked Questions about guru-smells

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

FAQPage Schema

What are code smells and how do they affect software maintainability?▼

Targeted refactoring patterns resolve code smells by restructuring object-oriented codebases. Treatments address root causes across categories like Bloaters and Change Preventers, improving maintainability and readability through prescribed structural corrections.

How do I fix Feature Envy and other object-oriented code smells?▼

Can I apply code smell detection to any object-oriented codebase?▼

Use categorized code smell catalogs during code reviews and onboarding to identify symptoms and apply concrete refactoring examples. This enforces best practices, improves code quality, and ensures architectural consistency across the team.

When should I refactor code smells during the development cycle?▼

What is the best way to categorize code smells for architectural planning?▼

Categorize code smells into Bloaters, Object-Orientation Abusers, Change Preventers, Dispensables, and Couplers. This structured classification links specific symptoms to targeted refactoring patterns, enabling actionable architectural planning and consistent remediation.