fallow

Detect dead code, duplicates, and architecture issues in JavaScript/TypeScript projects.

Updated Apr 23, 2025
One-click install
npx skills add https://github.com/xalixilax/react-hono-mono-starter --skill fallow-xalixilax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/xalixilax/react-hono-mono-starter/tree/main/.github/skills/fallow
Command: npx skills add https://github.com/xalixilax/react-hono-mono-starter --skill fallow-xalixilax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebase health analysis for JavaScript and TypeScript projects, identifying dead code, duplicates, circular dependencies, complexity hotspots, and architecture boundary issues to improve maintainability and reliability.

Core Features & Use Cases

  • High-signal dead-code detection across monorepos with auto-detection of plugins; check for unused exports, files, and dependencies; identify circular dependencies and architecture violations; surface complexity hotspots for targeted refactors; optionally merge production-coverage data for runtime analysis.
  • Use cases include auditing large codebases, preparing clean-ups before releases, and enforcing code health gates in CI.

Quick Start

Run fallow in your project root to perform a full health audit with zero-config defaults.

Frequently Asked Questions about fallow

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

FAQPage Schema
How do I detect dead code and unused exports in a TypeScript monorepo?

Dead code detection in a TypeScript monorepo is handled by running a static analysis audit that auto-detects plugins to surface unused exports, files, and dependencies across multiple packages with zero configuration.

What is the best way to find circular dependencies and architecture boundary violations in JavaScript?

Finding circular dependencies and architecture boundary violations in JavaScript requires a code health analytics audit that identifies structural issues across packages to improve maintainability and reliability.

How do I enforce code health gates in CI using static analysis for JavaScript projects?

To enforce code health gates in CI for JavaScript projects, run a static analysis audit that outputs rich JSON data suitable for automation, identifying complexity hotspots and duplication before releases.

Can I integrate production coverage data to improve dead code detection accuracy?

Production coverage data can be optionally merged into the static analysis to correlate runtime behavior with unused exports, filtering out false positives and refining dead code detection results.

Does this static analysis tool work with zero configuration out of the box?

Zero configuration is supported out of the box, allowing you to run the tool directly in your project root to perform a full health audit with auto-detection of plugins and default settings.

How do I identify complexity hotspots for targeted refactoring in a web application?

Identifying complexity hotspots for targeted refactoring in a web application involves running a codebase health analysis that surfaces high-complexity areas and architectural issues for clean-up.