fallow

Analyze TypeScript/JavaScript codebases for dead code and dependency issues.

2|Updated May 15, 2026

Search Tags:#code quality #static analysis #TypeScript #code audit #JavaScript

Ready to run

npx skills add https://github.com/bdbch/ai-dotfiles --skill fallow-bdbch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fallow
Source: https://github.com/bdbch/ai-dotfiles/tree/main/skills/fallow
Command: npx skills add https://github.com/bdbch/ai-dotfiles --skill fallow-bdbch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of manually auditing and reviewing TypeScript/JavaScript codebases for dead code, unused dependencies, circular dependencies, code duplication, and complexity hotspots.

Core Features & Use Cases

Codebase Audits: Review changesets or entire codebases for issues.
Health Checks: Provide a comprehensive health score for the codebase.
Use Case: Use fallow to ensure your project is free of errors and inefficiencies before deploying or merging changes.

Quick Start

Run 'fallow audit' to audit the current changes or 'fallow health' for a whole-codebase health check.

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 circular dependencies in a TypeScript project?▼

You can identify dead code and circular dependencies in a TypeScript project by running a static analysis codebase audit. This process scans your code to detect unused dependencies, code duplication, and complexity hotspots.

What is the best way to check codebase health before merging changes?▼

The best way to check codebase health before merging changes is to perform a static analysis audit on your changeset. This reviews the code for errors and inefficiencies, providing a comprehensive health score for your project.

Does static analysis for JavaScript require any specific project setup?▼

Static analysis for JavaScript requires a project with a package.json file. You also need the specific CLI tool installed to execute the audit and health check commands within your codebase.

Can I use code auditing tools in continuous integration workflows?▼

Yes, you can use code auditing tools in continuous integration workflows. The static analysis is designed for code review processes, allowing you to automate checks for dead code and complexity hotspots.

How do I run a full codebase audit for unused dependencies?▼

To run a full codebase audit for unused dependencies, execute a whole-codebase health check command. This static analysis identifies unused dependencies, code duplication, and complexity hotspots across the entire project.