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 fallow recommend or pnpm dlx fallow recommend. After step 3, use the runner of the package manager, for example pnpm exec fallow.

Sequence