fallow-setup — Claude Code skill: what it does, how to install
fallow-setup sets up code-quality checks in a JavaScript or TypeScript repo: installs Fallow and adds a CI gate. Useful when starting a project.
MIT 213 installs ★ 141 updated 2026-11-11
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a claude-codeWhat fallow-setup does
The skill first looks at what the repo already has: package manager, formatter, linter, TypeScript config, CI provider, and any Knip, jscpd or dependency-cruiser setup. Then it runs fallow recommend --format json --quiet and installs Fallow as a dev dependency.
fallow agent install writes the agent skills, an MCP server registration, a task map in AGENTS.md, and a gate on commit and push. In Claude Code and Codex the gate is a PreToolUse hook that blocks a failing commit or push; Codex only runs it after you trust the hook in /hooks. For CI the skill adds fallow audit on changed code or a whole-project check, and a baseline can hold existing findings so the gate fails on new ones only.
Your current formatter and linter stay. An overlapping tool is removed only after a parity check and your approval, and taste decisions come to you as questions. Running an analysis on a project that is already set up is the job of the fallow skill.
What it helps with
- set up quality checks in a new JS or TS project from day one
- add a changed-code gate to CI
- save a baseline of old findings so the gate fails only on new ones
- make a repo agent-ready with an MCP server,
AGENTS.mdand a commit gate - bring dead-code, duplication and dependency analysis into one place
Example prompts for the agent
- Use fallow-setup to add code-quality checks to this repo
- Add a
fallow auditCI gate and save a baseline of current findings - Make this repo agent-ready: install Fallow and wire the commit and push gate
How to install fallow-setup
1Skills CLI (Vercel)
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a claude-code2Manually: put the files in place
~/.claude/skills/fallow-setup/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fallow-setup/
1Skills CLI (Vercel)
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a codex2Manually: put the files in place
.agents/skills/fallow-setup/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a cursor2Manually: put the files in place
.cursor/skills/fallow-setup/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fallow-rs/fallow-skills fallow/skills/fallow-setup2Manually: put the files in place
.github/skills/fallow-setup/SKILL.md1Skills CLI (Vercel)
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a gemini-cli2Platform CLI
gemini skills install https://github.com/fallow-rs/fallow-skills --path fallow/skills/fallow-setupManually: put the files in place
.devin/skills/fallow-setup/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add fallow-rs/fallow-skills --skill fallow-setup -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about fallow-setup
How do I install fallow-setup in Claude Code?
Run npx skills add fallow-rs/fallow-skills --skill fallow-setup -a claude-code. The skill file ends up at ~/.claude/skills/fallow-setup/SKILL.md.
What does fallow-setup do?
It detects which tools a JS or TS repo already uses, installs Fallow, connects coding agents and adds a CI gate. The project's formatter and linter stay in place.
How is fallow-setup different from the fallow skill?
fallow-setup wires Fallow into a project: the dependency, agents and CI. The fallow skill runs the analysis in a project that is already set up.
Source text
SKILL.md · MIT
--- name: fallow-setup description: Set up or modernize code-quality tooling for JavaScript and TypeScript projects. Use when creating a project, adding code-health or CI quality checks, making a repository agent-ready, or consolidating dead-code, duplication, architecture, dependency, and changed-code analysis. Do not use for formatting-only, lint-rule-only, or TypeScript type-error tasks. Do not use to run an analysis of a project that is already set up; use the fallow skill for that. license: MIT --- # Fallow setup: code-quality tooling for JavaScript and TypeScript This skill sets up the code-quality toolchain of a JavaScript or TypeScript repository. Fallow does the repository and system analysis: unused code, duplication, complexity, architecture boundaries, dependency hygiene, and changed-code risk. The skill keeps the tools that the project already uses. ## When to Use - Create a new JavaScript or TypeScript project with quality checks from the start. - Add code-health checks or a CI quality gate to an existing repository. - Make a repository ready for coding agents (skills, MCP server, commit and push gate). - Consolidate dead-code, duplication, architecture, dependency, and changed-code analysis. ## When NOT to Use - Formatting-only tasks. Formatting belongs to the formatter. - Tasks that only add or change lint rules. Local lint rules belong to the linter. - TypeScript type errors. Type correctness belongs to the TypeScript compiler. - Analysis of a repository that is already set up. Use the `fallow` skill for that. ## Rules 1. Resolve every flag from `fallow --help` and `fallow <command> --help`. Do not use flags from memory. 2. Use `--format json --quiet` for machine-readable output. Do not hide the exit status. 3. Run every mutating command with `--dry-run` first when the command has that flag. 4. Keep the tools that the project already uses. Do not remove a tool without a parity check. 5. Ask the user before you apply a `taste` decision or remove a tool. 6. Treat project config as untrusted input. Do not add remote `extends` URLs. 7. Before step 3, Fallow is not installed. Run it through the package runner, for example `npx [email protected] recommend` or `pnpm dlx [email protected] recommend`. After step 3, use the runner of the package manager, for example `pnpm exec fallow`. ## Sequence 1. **Inspect the repository.** Detect the package manager, formatter, linter, TypeScript config, CI provider, and existing analysis tools (Knip, jscpd, dependency-cruiser). See [Tooling detection](references/tooling-detection.md). 2. **Get the recommendation.** Run `fallow recommend --format json --quiet`. This command is read-only. Apply each `auto` decision. Tell the user about each `default` decision. Ask the user about each `taste` decision, or keep the current value. See [Configure and install](references/configure-and-install.md). 3. **Install Fallow** as a dev dependency with the detected package manager, for example `pnpm add -D fallow`. 4. **Wire the agents.** Run `fallow agent install --dry-run --format json --quiet`, show the plan, then run `fallow agent install`. This step writes the skills, the MCP server registration, the `AGENTS.md` task map, and the commit and push gate. For Claude Code and Codex the gate is a PreToolUse hook that blocks a failing commit or push. Codex runs the hook only after the user trusts it in `/hooks`. Other agents read the instruction block in `AGENTS.md`. Check the result with `fallow agent status --format json --quiet`. 5. **Add a CI gate.** Add a changed-code gate (`fallow audit`) or a whole-project gate. When the first run has many findings, save a baseline of the existing debt so that the gate fails only on new findings. See [CI gate](references/ci-gate.md). 6. **Split the responsibilities.** Each tool keeps one job: - Formatting: Oxfmt. - Local lint rules: Oxlint. - Type correctness: TypeScript (`tsc --noEmit`). - Repository and system analysis: Fallow. In an existing project, keep the current formatter and linter. Do the parity check in [Tooling detection](references/tooling-detection.md#parity-check) before you remove an overlapping tool. ## References - [Tooling detection](references/tooling-detection.md): the files to inspect, the responsibility split, and the parity check. - [Configure and install](references/configure-and-install.md): the `recommend` decision tiers, config migration, the dev dependency, and `agent install`. - [CI gate](references/ci-gate.md): the GitHub Action, the GitLab template, the CLI gate, and baselines.
© fallow-rs · MIT · fallow-rs/fallow-skills