Install fallow analysis skills for Claude Code, Cursor, Windsurf, Gemini CLI, and other AI agents that support the Agent Skills specification.
Agent skills give AI coding agents structured knowledge about how to use fallow. Skills cover when to run each command, what flags to use, how to read the output, and how to avoid common pitfalls. Instead of relying on the agent’s general knowledge, skills provide precise, up-to-date instructions for codebase health, cleanup analysis, circular dependency detection, duplication, and complexity hotspots.
Skills work alongside the CLI and MCP integrations. They tell agents how to use fallow effectively, while the CLI and MCP provide the tools to do it.
When the goal is to bring an existing codebase to a clean Fallow policy (not just audit a single PR), fallow’s approach is to hand the cleanup work to the agent: fallow finds the problems, the agent fixes them in code.Three ways to run this, pick whichever your agent supports:
Install the skill (best). fallow-skills ships the full adoption workflow. Once installed, the agent does not need to fetch docs URLs during use. Installation is one line per agent, above.
Add the MCP server. Combine with the skill or use standalone. The agent gets audit, dead_code, dupes, and health as structured tools with _meta explanations on every finding. See MCP.
Paste the prompt below. Self-contained fallback for agents without skill or MCP support, or for sandboxed agents that cannot fetch URLs.
Copy-paste adoption prompt (self-contained)
Adopt Fallow in this repository.Goal:- use full-repo analysis first (`fallow`, `fallow dead-code`, `fallow dupes`, `fallow health`), not `fallow audit`- fix real dead code, duplication, and complexity issues in code- model intentional exceptions with the narrowest correct mechanism- end with no functions above the repo's chosen health thresholds, or a consciously widened threshold with written justification- then set up `fallow audit` as a PR gateProcess:1. Run `npx fallow`, then `npx fallow dead-code`, `npx fallow dupes`, and `npx fallow health`. Use `--format json` for structured output.2. If no config exists, run `fallow init` and create a minimal repo policy.3. Fix high-confidence issues first: - unresolved imports - unlisted dependencies - unused files (sanity-check with `fallow list --entry-points`) - unused dependencies4. For each remaining finding, choose one path: - fix it in code (preferred) - model it in config - add a narrow inline exception only if it is truly one-off5. Match reasons to mechanisms: - external API: `@public` / `@internal` / `@beta` / `@alpha` JSDoc tags, or `publicPackages` - runtime or framework entry point: `entry`, `dynamicallyLoaded`, plugin-aware config - generated code: `ignorePatterns`, `health.ignore` - intentionally retained dependency: `ignoreDependencies` - intentional unused export: `@expected-unused` (preferred over inline comments because it self-cleans) - one-off false positive: `fallow-ignore-next-line` - repo-wide policy: `rules`, `health`, duplication settings, `overrides`6. Prefer config-level modeling over repeated suppression.7. Keep every exception narrow and explain why it exists in a commit message.8. Re-run Fallow after each batch until the repo is clean under the chosen policy.9. Only after repo cleanup, run `npx fallow audit` and wire it into CI.At the end, report:- code changes- config changes- exceptions added and why- anything left- the final commands and outputs that show the repo is clean
For the best experience, combine all three. Install the skill for knowledge, configure MCP for structured tool calling, and keep fallow in PATH for CLI fallback.
