fallow

Analyze JavaScript or TypeScript repositories for unused code and structural issues.

Updated May 23, 2026
One-click install
npx skills add https://github.com/matthewharwood/dean-n-dean --skill fallow-matthewharwood
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/matthewharwood/dean-n-dean/tree/main/.agents/skills/fallow
Command: npx skills add https://github.com/matthewharwood/dean-n-dean --skill fallow-matthewharwood

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fallow helps you identify unused code and structural issues in JavaScript and TypeScript so you can safely clean a codebase instead of relying on guesswork or brittle manual reviews.

Core Features & Use Cases

  • Dead code intelligence: Detects unused files, unused exports, unused types, unused dependencies, unresolved imports, and duplicate exports.
  • Architecture and quality signals: Finds circular dependencies and architecture boundary violations to prevent long-term coupling drift.
  • Complexity hotspots: Highlights complexity-heavy functions and maintainability pressure, with optional runtime coverage integration for higher confidence deletion decisions.
  • Guided, safe fixes: Supports dry-run previews and controlled auto-fixes so you can apply changes confidently.

Quick Start

Run fallow dead-code for machine-readable results and review the JSON output for what can be removed.

Frequently Asked Questions about fallow

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

FAQPage Schema
How do I find and safely delete dead code in a JavaScript or TypeScript repository?

Dead code intelligence detects unused files, exports, types, and unresolved imports in JavaScript and TypeScript codebases. It supports safe deletion through dry-run validation and controlled auto-fixes, ensuring you remove unreachable modules confidently without breaking functionality.

Can I use a dependency audit tool to detect circular dependencies and architecture boundary violations?

Yes, a dependency audit detects circular dependencies and architecture boundary violations to prevent long-term coupling drift. It also identifies complexity hotspots and duplication, providing structural quality signals to maintain code health across your project.

How do I set up a CI quality gate to catch structural regressions and unused exports?

Set up a CI quality gate by running structural analysis with JSON-only quiet execution and exit-code semantics. This configuration fails pipelines automatically when unused exports, circular dependencies, or boundary violations are detected, preventing structural regressions.

Does dead code analysis work for auditing a monorepo and checking workspace-specific hygiene?

Yes, dead code analysis supports auditing a monorepo for workspace-specific hygiene. It evaluates the repository to find unreachable modules, unused dependencies, and duplicate exports across workspaces, making it ideal for release preparation or post-refactor cleanup.

What is the best way to auto-fix unused code without risking runtime errors?

The best way to auto-fix unused code safely is using controlled application with dry-run validation. This approach previews changes before applying them and relies on exit-code semantics to distinguish between detected issues and actual runtime errors.