fallow

Codebase intelligence for TypeScript and JavaScript. Static analysis of code and styles reports changed-code risk, cleanup opportunities, duplication, circular dependencies, complexity hotspots, architecture boundaries, design-system drift, feature flags, and opt-in security candidates. Runtime coverage can merge production execution data for hot-path review, cold-path deletion confidence, and stale-flag evidence. 123 framework plugins, zero configuration, sub-second static analysis. Use when asked to audit PR risk, find unused code or dependencies, detect duplicates, check styling consistency, inspect architecture boundaries, merge runtime coverage, auto-fix supported issues, or run fallow.

Select the minimum complete reviewer team for a Fallow change based on touched paths, contracts, integrations, and risk.

Audit the current Fallow session for missed work, incomplete verification, stale documentation, companion drift, or cleanup before final completion.

Measure Fallow maintainability using the repository's SIG system properties and update the evidence-backed audit report.

Iteratively improve Fallow maintainability using measured SIG audit deltas, retaining only changes that improve the targeted property without regressions.

Land completed Fallow work after review, run pre-push parity, monitor merged-commit CI, and leave repositories clean. Use when asked to ship, merge, or move approved work to main.

Perform Fallow's comprehensive pre-merge review. Use after implementation or when asked to review a branch, pull request, or diff.

Prepare and publish a Fallow release with version, changelog, generated contracts, companion repositories, registry publication, and post-release verification.

Iteratively optimize Fallow performance with stable benchmarks, before-and-after evidence, and correctness gates.

Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or user experience with representative end-user and domain-expert perspectives before implementation.

Iteratively review and improve a Fallow user-facing surface across representative real-world projects until the panel has no blocking concerns.

Research, implement, test, document, and review a Fallow feature, fix, refactor, or repository improvement. Use when asked to build or change Fallow.

Diagnose and fix a Fallow false positive or false negative through extraction, resolution, graph, analysis, reporting, and real-consumer verification.

Iteratively improve Fallow Rust test coverage with cargo-llvm-cov, prioritizing meaningful untested behavior and preserving runtime correctness.

Iteratively improve Fallow analysis accuracy by comparing it with competing tools and verified source truth across a stable real-world corpus.

Iteratively reduce Fallow binary size using cargo-bloat and release-build measurements while preserving features, performance, and compatibility.

Select the minimum complete reviewer team for a Fallow change based on touched paths, contracts, integrations, and risk.

Audit the current Fallow session for missed work, incomplete verification, stale documentation, companion drift, or cleanup before final completion.

Measure Fallow maintainability using the repository's SIG system properties and update the evidence-backed audit report.

Iteratively improve Fallow maintainability using measured SIG audit deltas, retaining only changes that improve the targeted property without regressions.

Land completed Fallow work after review, run pre-push parity, monitor merged-commit CI, and leave repositories clean. Use when asked to ship, merge, or move approved work to main.

Perform Fallow's comprehensive pre-merge review. Use after implementation or when asked to review a branch, pull request, or diff.

Prepare and publish a Fallow release with version, changelog, generated contracts, companion repositories, registry publication, and post-release verification.

Iteratively optimize Fallow performance with stable benchmarks, before-and-after evidence, and correctness gates.

Review a Fallow design, plan, workflow, CLI surface, documentation architecture, or user experience with representative end-user and domain-expert perspectives before implementation.