fallow
fallow
What it does
- Find cleanup opportunities: unused files, exports, types, members, dependencies, or stale flags.
- Detect code duplication, circular dependencies, architecture boundary issues, and complexity hotspots.
- Check styling consistency, CSS dead surface, and design-token drift.
- Audit changed code before a commit, PR, release, or refactor.
- Set up CI quality gates, duplication thresholds, and regression baselines.
- Auto-fix supported unused exports and dependencies after --dry-run.
- Investigate why a specific export, dependency, file, or issue type was reported.
Requirements & configuration
- Check styling consistency, CSS dead surface, and design-token drift.
- | unused-store-member | --unused-store-members | - | // fallow-ignore-next-line unused-store-member | Pinia store state/getter/action (needs pinia dep) |
- | boundary-call-violation | --boundary-violations | - | // fallow-ignore-next-line boundary-call-violation | Zoned file calls a callee its zone forbids; Requires boundaries.calls.forbidden patterns |
- | invalid-client-export | - | - | // fallow-ignore-next-line invalid-client-export | "use client" file exports a server-only / route-config name; Requires the project to declare next |
- | unused-svelte-event | --unused-svelte-events | - | // fallow-ignore-next-line unused-svelte-event | A Svelte createEventDispatcher event is listened to nowhere in the project; needs svelte dep |
Configuration: FALLOW_AGENT_SOURCEFALLOW_CA_BUNDLEARGUMENTS
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
fallow FAQ
What does the fallow skill do?
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. Find cleanup opportunities: unused files, exports, types, members, dependencies, or stale flags. Detect code duplication, circular dependencies, architecture boundary issues, and complexity hotspots.
What does fallow require?
Check styling consistency, CSS dead surface, and design-token drift. | unused-store-member | --unused-store-members | - | // fallow-ignore-next-line unused-store-member | Pinia store state/getter/action (needs pinia dep) | | boundary-call-violation | --boundary-violations | - | // fallow-ignore-next-line boundary-call-violation | Zoned file calls a callee its zone forbids; Requires boundaries.calls.forbidden patterns | | invalid-client-export | - | - | // fallow-ignore-next-line invalid-client-export | "use client" file exports a server-only / route-config name; Requires the project to declare next | | unused-svelte-event | --unused-svelte-events | - | // fallow-ignore-next-line unused-svelte-event | A Svelte createEventDispatcher event is listened to nowhere in the project; needs svelte dep | Configuration keys: FALLOW_AGENT_SOURCE, FALLOW_CA_BUNDLE, ARGUMENTS.
How do I install fallow?
Run: npx -y skills add https://github.com/fallow-rs/fallow-skills --skill fallow --agent claude-code — the source lives at github.com/fallow-rs/fallow-skills.
Maintain fallow?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[](https://getagentictools.com/skills/fallow-rs-fallow-skills-fallow?ref=badge) npx agentictools info skills/fallow-rs-fallow-skills-fallow The second line is the CLI lookup for this page — handy in READMEs and docs.