smell

Detects architecture and code smells and produces a markdown report.

207|30|Updated May 16, 2026
One-click install
npx skills add https://github.com/smallnest/goal-workflow --skill smell-smallnest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smell
Source: https://github.com/smallnest/goal-workflow/tree/main/skills/smell
Command: npx skills add https://github.com/smallnest/goal-workflow --skill smell-smallnest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams identify architecture, coupling, cohesion, design, testing, naming, and complexity problems in a codebase before they become expensive to change.

Core Features & Use Cases

  • Scans a project or scoped directory for anti-patterns such as Big Ball of Mud, circular dependencies, God Objects, duplicated code, and N+1 query patterns.
  • Produces an actionable markdown report with severity levels, evidence, module health scores, dependency analysis, and a refactoring roadmap.
  • Useful when you need a quick architecture health check, a review of recent changes, or a deep dive into problematic modules.

Quick Start

Ask the smell skill to analyze the entire project and generate a markdown report with the most important architecture and code smells.

Frequently Asked Questions about smell

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

FAQPage Schema
How do I detect architecture and code smells in a codebase?

To detect architecture and code smells in a codebase, run a full-project scan that identifies anti-patterns like God Objects and circular dependencies. The analysis produces a structured markdown report with severity ratings, evidence, and a refactoring roadmap.

What are common code anti-patterns found during a codebase review?

Common code anti-patterns found during a codebase review include Big Ball of Mud, circular dependencies, God Objects, duplicated code, and N+1 query patterns. Identifying these architecture and code smells early helps prevent expensive changes later.

How do I generate a refactoring roadmap for problematic modules?

You generate a refactoring roadmap for problematic modules by performing a deep dive complexity hotspot detection analysis. This creates an actionable markdown report featuring module health scores, dependency analysis, and severity levels to guide your refactoring efforts.

Can I scan recent code changes for anti-patterns instead of the full project?

Yes, you can scan recent code changes for anti-patterns instead of the full project. The analysis applies to scoped module reviews and recent-change analysis, producing a focused markdown report with evidence and severity ratings for the targeted modifications.

What is included in a module health scorecard for architecture analysis?

A module health scorecard for architecture analysis includes severity ratings, evidence of code smells, and dependency analysis. It evaluates coupling, cohesion, design, testing, naming, and complexity problems to produce an actionable refactoring roadmap.