skills.rest
skyosev
skyosevCOMMUNITY
Explore all skills by this author →
GitHub

smell-hunter-ts

Detect common TypeScript code smells and output a structured report.

5|Updated Jan 14, 2026
Search Tags:#typescript#design#audit#refactor#code-quality#static-analysis#code-smell
One-click install
npx skills add https://github.com/skyosev/agent-skills --skill smell-hunter-ts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smell-hunter-ts
Source: https://github.com/skyosev/agent-skills/tree/main/hunter-party-ts/smell-hunter-ts
Command: npx skills add https://github.com/skyosev/agent-skills --skill smell-hunter-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript codebases often conceal design issues that erode maintainability. This skill identifies classic smells (e.g., feature envy, data clumps, shotgun surgery, primitive obsession, temporal coupling, and more) and surfaces actionable signals with evidence to drive refactoring decisions.

Core Features & Use Cases

  • Detects a broad set of TypeScript smells including data clumps, feature envy, temporal coupling, temporary fields, and callback chains.
  • Aids code reviews, design audits, and refactor planning by providing concrete signals and suggested improvements.
  • Supports teams aiming to improve cohesion, reduce cross-module dependencies, and clarify domain concepts.

Quick Start

Scan a TypeScript project to surface the most relevant smells and guide a refactor.

Frequently Asked Questions about smell-hunter-ts

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

FAQPage Schema
How do I detect TypeScript code smells like feature envy and primitive obsession in my project?▼

TypeScript code smell detection analyzes your source files to surface issues like feature envy, primitive obsession, and callback hell, providing a structured report with evidence for refactoring.

What TypeScript design issues should I look for during a code review or architecture audit?▼

During a TypeScript code review, you should look for common smells such as data clumps, shotgun surgery, temporal coupling, and temporary fields that erode maintainability and increase cross-module dependencies.

Can I scan a TypeScript codebase for callback hell and data clumps to plan a refactor?▼

Yes, you can scan a TypeScript codebase to detect callback hell and data clumps, which outputs a structured report with suggested actions to clarify domain concepts and improve code cohesion.

Does this code smell analysis require any external dependencies or specific TypeScript configurations?▼

This code smell analysis requires no external dependencies and operates directly on TypeScript sources, analyzing the codebase structure to identify design flaws without needing specific configuration setups.

What is the best way to find temporal coupling and shotgun surgery in TypeScript code?▼

The best way to find temporal coupling and shotgun surgery is to run a static analysis scan on your TypeScript sources, which surfaces these structural flaws with actionable signals and suggested improvements.

Related Skills

Explore More Software Engineering Skills→
Long-NguyenHaiLong-NguyenHai

coding-standards

Enforce coding conventions and code quality for JavaScript and TypeScript projects.

Community
Advanced
thoreinsteinthoreinstein
5

refactor

Analyze Go and frontend codebases to identify refactoring opportunities and rationale.

Community
Advanced
markhamsquareventuresmarkhamsquareventures

pint

Format Laravel PHP code automatically using Pint styling rules.

Official
Intermediate
vosslabvosslab
2

typescript-engineer

Resolve TypeScript compiler errors and design strict generic types.

Community
Advanced