fallowlisted

Codebase intelligence for JavaScript and TypeScript. Free static layer reports quality, changed-code risk, cleanup opportunities (unused files, exports, types, dependencies), code duplication, circular dependencies, complexity hotspots, architecture boundary violations, feature flag patterns, and opt-in security candidates. Runtime coverage merges production execution data into the same health report for hot-path review, cold-path deletion confidence, and stale-flag evidence, with a single local capture available by default and continuous/cloud runtime monitoring available as an optional mode. 118 framework plugins, zero configuration, sub-second static analysis. Use when asked to analyze code health, audit PR risk, find cleanup opportunities or unused code, detect duplicates, check circular dependencies, audit complexity, check architecture boundaries, detect feature flags, surface security candidates, clean up the codebase, auto-fix issues, merge runtime coverage, or run fallow.
DamengRandom/oh-my-workers · ★ 0 · AI & Automation · score 63

Install: claude install-skill DamengRandom/oh-my-workers

# Fallow: codebase intelligence for JavaScript and TypeScript Codebase intelligence for JavaScript and TypeScript. The free static layer reports quality, changed-code risk, cleanup opportunities, circular dependencies, code duplication, complexity hotspots, architecture boundary violations, feature flag patterns, and opt-in security candidates. Runtime coverage merges production execution data into the same `fallow health` report for hot-path review, cold-path deletion confidence, and stale-flag evidence, with a single local capture available by default and continuous/cloud runtime monitoring available as an optional mode. 118 framework plugins, zero configuration, sub-second static analysis. ## When to Use - Finding cleanup opportunities (unused files, exports, types, enum/class members) - Finding unused or unlisted dependencies - Detecting code duplication and clones - Checking code health and complexity hotspots - Cleaning up a codebase before a release or refactor - Auditing a project for structural issues - Setting up CI quality gates or duplication thresholds - Auto-fixing unused exports and dependencies - Detecting feature flag patterns (environment gates, SDK calls, config objects) - Investigating why a specific export or file appears unused ## When NOT to Use - Runtime error analysis or debugging - Type checking (use `tsc` for that) - Linting style or formatting issues (use ESLint, Biome, Prettier) - Verified security vulnerability scanning or SAST. `fallow secu