Skip to content
Fallow home
GitHub
All docs pages

CLI reference

The CLI reference pages of the Fallow documentation.

  • fallow dead-code: Find the files, exports, dependencies, and types that nothing uses, so you can delete them. Fallow dead-code starts at your entry points, traces reachable exports, and reports the rest.
  • fallow dupes: Find copy-pasted code that you can merge into one shared function. Fallow dupes detects duplicated code blocks across your codebase with suffix-array analysis and configurable thresholds.
  • fallow viz: See where dead code, duplication, boundary violations, and complexity sit in your codebase. Fallow viz writes one self-contained HTML map with a file treemap and an import graph.
  • fallow health: Find the functions and files that are hardest to maintain and the best places to refactor first, from complexity, git churn, and coverage. CLI reference for fallow health.
  • fallow license: Turn on continuous and multi-capture runtime coverage on your machine or CI runner. Fallow license activates a trial or JWT, shows status, refreshes a license, or deactivates the local token.
  • fallow telemetry: Control what fallow sends, and see the exact payload before it leaves your machine. Fallow telemetry manages opt-in product telemetry, which is off by default: check status, enable, disable, or inspect.
  • fallow coverage: Use production runtime data to see which code runs and which code you can delete. Fallow coverage runs the resumable setup flow, analyzes local or cloud runtime coverage, uploads source maps, and uploads the static inventory that shows untracked code in the dashboard.
  • fallow flags: Find the feature flags in your codebase, so you can review them. Fallow flags detects environment variable gates, SDK calls, and config-based toggles.
  • fallow security: Find local security candidates for you or a coding agent to verify: server secrets that reach client code, and untrusted values that reach dangerous sinks. CLI reference for the opt-in fallow security command.
  • Security agent verification: Cut fallow security candidates down to a short list of survivors that a verifier could not dismiss. Fallow itself makes no model calls.
  • fallow audit: Get one pass, warn, or fail verdict for the files a PR changes, from dead code, complexity, duplication, and styling checks. CLI reference for fallow audit, the quality gate for PRs and AI-generated code review.
  • fallow mutation: Check whether your tests fail when the changed code is wrong. fallow mutation makes small changes to your code, runs your Vitest, node:test, or bun test tests against each one, and reports the changes that no test detects.
  • fallow impact: See what fallow has done for you in a project. Fallow impact is a local-only report of current findings, the trend, commits stopped at the gate, and findings resolved over time.
  • fallow inspect: Get all the context for one file or exported symbol before you edit it. Fallow inspect combines trace, dead-code, duplication, complexity, and security evidence in one bundle.
  • fallow trace: See what calls an exported symbol and what it calls before you change it, or find how one module comes to import another. Fallow trace is a best-effort command, separate from the ranked review brief.
  • fallow trace-error: Go from a runtime stack trace to the definitions in your code that its frames name. Fallow trace-error resolves each frame against the module graph, without reading source maps.
  • fallow decision-surface: Get the few structural decisions in a change that need a human judgment call, each as a question with the expert to ask. CLI reference for fallow decision-surface, the top layer of the review brief printed alone.
  • fallow explain: Learn what a fallow finding means and how to fix it, without running analysis. Fallow explain prints the rationale, an example, fix guidance, and a docs link for one issue type.
  • fallow fix: Remove unused exports and dependencies without editing each file by hand. Fallow fix edits your source files in place, with a dry-run preview and JSON output.
  • fallow watch: Get dead code results each time you save a file. Fallow watch re-runs dead code analysis when files change.
  • fallow init: Start a fallow config with editor autocomplete and validation. Fallow init generates a .fallowrc.json or fallow.toml configuration file with schema support.
  • fallow agent: Set up fallow for Claude Code, Codex, and Cursor with one command. Fallow agent installs the AGENTS.md task map, the skill, the MCP server registration, and the commit and push gate, and can show status or uninstall.
  • fallow recommend: Get a config proposal for your project that you can review before you write it. Fallow recommend is read-only and reports what fallow detected, a safe proposed config, and the decisions behind it, split into auto, default, and taste.
  • fallow doctor: Find out if fallow can see your project correctly before you trust its results. Fallow doctor runs read-only checks on the project root, config, workspaces, plugins, the optional type-aware companion, dependencies, and caches.
  • fallow guard: Know the architecture rules for a file before you edit it. Fallow guard reports the boundary zone, the zones the file can import from, the forbidden calls, and the rule-pack policies with their suppression tokens.
  • fallow architecture: Check the structure of your code after an edit. Fallow architecture reports circular dependencies, re-export cycles, package cycles, boundary violations, and rule-pack policy violations.
  • fallow plugin-check: Find out why a custom plugin does not activate or seeds no entries. Fallow plugin-check is a read-only dry run that reports, for each external plugin, if it activated and what each manifestEntries rule matched and seeded.
  • fallow migrate: Move to fallow and keep the settings you already have. Fallow migrate converts your existing knip, jscpd, or stylelint configuration to the fallow config format.
  • fallow list: See what fallow found in your project, so you can debug the configuration and check the project setup. Fallow list shows discovered files, entry points, active plugins, boundary zones, workspaces, and the startup import weight of each entry.
  • fallow config: Find out why your config is not applied. Fallow config shows the resolved fallow config and which file was loaded, like eslint --print-config and dprint output-resolved-config.
  • fallow schema: Let an agent learn everything fallow can do from one JSON document. Fallow schema prints the complete capability manifest: commands, issue types, MCP tools, plugins, and environment variables.
  • fallow suppressions: See every finding your team chose to ignore, and why. Fallow suppressions is a read-only inventory of each active fallow-ignore marker, grouped by file with kind, level, and reason, plus project totals and a stale count.
  • fallow baselines prune: Remove the entries of fixed findings from committed fallow baselines. One whole-project run prunes the dead-code, health and duplication baselines, never adds an entry, and keeps the stale-baseline gate green.
  • fallow report: Analyze once, then produce every CI output from the saved result. Fallow report renders saved JSON results as CI artifacts, summaries, PR comments, or inline-review envelopes without re-running analysis.
  • Global flags: Control the project root, config, output format, scope, cache, and CI gates the same way on every fallow command. Reference for the shared CLI flags, including workspace, changed-workspaces, score, trend, and snapshot options.