Agent skills for the fallow codebase intelligence layer for TypeScript and JavaScript. Agent skills for fallow, codebase intelligence for TypeScript and JavaScript. The static layer reports quality, changed-code risk, cleanup opportunities, circular dependencies, code duplication, complexity hotspots, architecture boundary violations, and design-system styling drift in milliseconds. Fallow Cloud, the optional paid…
Agent skills for fallow, codebase intelligence for TypeScript and JavaScript. Teaches AI agents how to find unused code, duplication, circular deps, complexity hotspots, architecture drift, design-system drift, and (with Fallow Runtime) hot-path and cold-path evidence. Works with Claude Code, Cursor, Codex, Gemini CLI, and 30+ agents.
Agent skills for the fallow codebase intelligence layer for TypeScript and JavaScript.
Agent skills for fallow, codebase intelligence for TypeScript and JavaScript. The static layer reports quality, changed-code risk, cleanup opportunities, circular dependencies, code duplication, complexity hotspots, architecture boundary violations, and design-system styling drift in milliseconds. Fallow Cloud, the optional paid product, adds production coverage so agents can delete cold code and flag hot-path changes with proof. Broad framework plugin coverage, zero configuration. Works with any agent that supports the Agent Skills specification: Claude Code, Cursor, OpenAI Codex, Windsurf, GitHub Copilot, Gemini CLI, Amp, and 30+ more. See Fallow for coding agents for the visual overview and store links.
Linters enforce style. Formatters enforce consistency. Fallow enforces relevance. Linters work file by file. TypeScript works type by type. Neither builds the full module graph, so neither can see what nothing depends on. Fallow does, in milliseconds. These skills teach agents how to use fallow effectively: which commands to run, what flags to use, how to interpret output, and how to avoid common pitfalls.
In the Codex desktop app, this install also adds the Fallow app: a code
health dashboard in the sidebar, a Code Health tab beside each thread,
@Fallow mentions for findings, a .fallowrc.json editor with an impact
preview, a .sarif viewer, a branch audit, and a cleanup planner that asks
you which findings to fix. Select findings to attach them to the composer, or
send them to Codex with one click. The app runs the fallow CLI on your machine,
inside the Codex sandbox of the thread when one is available. See
codex-app/README.md for every extension it uses.
Fallow Impact statusline
Claude Code users can add the compact Fallow Impact segment to their statusline:
/fallow:impact-statusline setup user compose
The command doc covers status,
remove, and the project scope. Other agents render the same line with
fallow impact statusline.
Use npx skills add fallow-rs/fallow-skills --all for installer-managed discovery, or copy the directories under fallow/skills/ into your agent’s skills location.
Prerequisites
Fallow must be installed in the target project:
npm install -g fallow # prebuilt binaries
npx fallow # or run without installing
See the installation guide for all options including cargo install fallow-cli.
Privacy and network behavior
Analysis runs locally by default and telemetry is off unless the user opts in.
The plugin README lists the exact network, telemetry, and
statusline behavior for the Claude Code and Codex surfaces.
Connect an app to Fallow Cloud: beacon with the commit SHA, inventory and source map uploads, deployment registration, and a check that the first data arrived
“set up Fallow Cloud”, “add the Fallow beacon”, “why does Fallow Cloud show no data”
Rust workspaces with cargo fallow: unused dependencies and files, visibility, boundaries, size, complexity, duplication, API changes and mutation testing
Codex only: set up the Fallow app after install, choose defaults, run the first analysis
“Set up” in the Codex plugin page, “set up the Fallow app”
Reference Documentation
CLI Reference: all commands, flags, JSON output structure, config format
Gotchas: common pitfalls with WRONG/CORRECT examples
Patterns: workflow recipes for CI, monorepos, migration, and incremental adoption
Contributing
See AGENTS.md for repository structure and quality standards.
Each skill listed in source-lock.json is vendored byte-for-byte from the
fallow source repository at the pinned commit. The cargo-fallow skill comes
from the cargo-fallow repository in the same way, with the pin in
cargo-fallow-source-lock.json. CI checks that pin against a
clean source checkout and rejects contract or privacy-boundary drift.
Maintainers can find the versioning, packaging, and store update procedure in
RELEASING.md.
Enable the commit hook
A fresh clone runs no hooks. Turn them on once per clone:
git config core.hooksPath .githooks
The hook checks new comments for edit history, manifest version agreement,
and the bump rule; see
.githooks/pre-commit for why it stops there.
Related
fallow: codebase intelligence for TypeScript and JavaScript, a single pass over code and styles
评论