fallow

Identify dead code, duplication, and complexity hotspots in TypeScript/JavaScript codebases.

143|52|Updated May 15, 2026
One-click install
npx skills add https://github.com/gotgenes/pi-packages --skill fallow-gotgenes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/gotgenes/pi-packages/tree/main/.pi/skills/fallow
Command: npx skills add https://github.com/gotgenes/pi-packages --skill fallow-gotgenes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface dead code, duplication, and high complexity in a TypeScript/JavaScript codebase to guide targeted refactors and improve maintainability.

Core Features & Use Cases

  • Finds unused code, duplicated blocks, and hotspots in large codebases (including monorepos).
  • Provides actionable targets for refactoring and health scoring across projects.
  • Works with pnpm-based workflows and root devDependencies to fit CI pipelines.

Quick Start

Run fallow on your TypeScript/JavaScript project to surface unused code, duplications, and complexity hotspots.

Frequently Asked Questions about fallow

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

FAQPage Schema
How do I find dead code and duplication in a TypeScript monorepo?

To find dead code and duplication in a TypeScript monorepo, run static analysis to surface unused code, duplicated blocks, and complexity hotspots. This provides actionable refactoring targets and health insights across large projects.

Can I integrate static code health analysis into a pnpm CI pipeline?

Yes, you can integrate static code health analysis into a pnpm CI pipeline by installing it as a root devDependency. This setup produces structured outputs suitable for CI tooling and automated refactoring checks.

What is static code health analysis for JavaScript and when do I need it?

Static code health analysis for JavaScript identifies dead code, duplication, and complexity hotspots to guide targeted refactors. You need it when maintaining large codebases or monorepos to improve overall code maintainability.

What's the best way to identify refactoring targets in a large JavaScript codebase?

The best way to identify refactoring targets in a large JavaScript codebase is applying static analysis to surface complexity hotspots and unused code. This approach provides actionable health scoring and specific areas for targeted improvements.

Does this static analysis tool work with both TypeScript and JavaScript projects?

Yes, this static analysis tool works with both TypeScript and JavaScript projects. It parses TS and JS codebases to identify dead code, duplication, and complexity hotspots, providing structured outputs for CI integration.