fallow

Analyze JavaScript and TypeScript codebases for dead code, duplication, and complexity hotspots.

111|9|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/fallow-rs/fallow-skills --skill fallow-fallow-rs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/fallow-rs/fallow-skills/tree/main/fallow/skills/fallow
Command: npx skills add https://github.com/fallow-rs/fallow-skills --skill fallow-fallow-rs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fallow provides automated codebase health analysis to identify dead code, duplication, and complexity hotspots in JavaScript/TypeScript projects, enabling teams to maintain healthier codebases and faster iteration.

Core Features & Use Cases

  • Dead code detection across files, exports, dependencies, and runtime signals.
  • Duplication detection with actionable highlights and remediation guidance.
  • Complexity and architecture health scoring to identify hotspots and boundary violations.
  • CI-friendly, deterministic outputs (JSON) and optional runtime-coverage integration for production insight.
  • Monorepo support with per-workspace scoping and cross-workspace graph resolution.

Quick Start

Run fallow in your project directory to perform a health check and view the JSON results.

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 duplication in a JavaScript project?▼

Dead code and duplication detection in JavaScript projects is automated by analyzing files, exports, and dependencies to identify unused modules and highlight actionable remediation targets.

Can I generate a codebase health score for a TypeScript monorepo?▼

Yes, codebase health scoring supports TypeScript monorepos by providing per-workspace scoping and cross-workspace graph resolution to pinpoint complexity hotspots and boundary violations.

Does dead code analysis work in CI pipelines with deterministic outputs?▼

Dead code analysis works in CI pipelines by producing deterministic, machine-readable JSON outputs and optional runtime-coverage integration to validate production usage signals.

What is the best way to identify complexity hotspots in TypeScript files?▼

Identifying complexity hotspots in TypeScript files is best handled by automated architecture health scoring, which evaluates code structure to expose high-compliance risk areas.

Do I need runtime-coverage integration to find dead code in JavaScript?▼

You do not need runtime-coverage integration to find dead code in JavaScript, as static analysis of files and exports suffices, though runtime signals enhance production insight.

Fallow for JavaScript: what limitations exist when analyzing cross-workspace dependencies?▼

Fallow for JavaScript resolves cross-workspace dependency graphs in monorepos, but limitations arise if runtime-coverage data is absent, restricting dead code validation to static signals.