Menu
Set up and optimize Knip configuration to find unused files, dependencies, and exports. Use when configuring knip.json or cleaning up a JavaScript or TypeScript codebase.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | configure-knip |
| description | Set up and optimize Knip configuration to find unused files, dependencies, and exports. Use when configuring knip.json or cleaning up a JavaScript or TypeScript codebase. |
Set up and iteratively optimize Knip configuration to find unused files, dependencies, exports, and types.
Ensure the @knip/mcp MCP server is registered in your AI coding agent:
npx -y @knip/mcp
This provides three MCP capabilities:
knip-configure prompt — guided workflow for setup and optimizationknip-run tool — runs analysis, returns configuration hints and issuesknip-docs tool — fetches Knip documentation by topicknip-configure MCP prompt — it contains the full workflow:
knip-docsknip-runknip.json)Clean up a git repository: delete branches whose PRs merged (incl. squash-merges), remove their safely removable linked worktrees, list or delete local branches past a confirmed age threshold, prune stale remote-tracking refs and worktree metadata, and optionally prune local tags absent from the remote, run gc, or delete merged remote branches. Use when asked to clean up / prune / tidy git branches or worktrees, remove merged or stale branches, delete old branches, prune origin/* refs, or clear out a repo's branch/worktree list, including from a directory containing worktrees from one or more repositories. Reports first (dry run); never touches current/default/kept branches or main, dirty, ignored-content, locked, detached, unavailable, or submodule-containing worktrees.
V8/Node.js performance patterns for hot paths, parsers, and core libraries in JavaScript/TypeScript. Use when writing or reviewing performance-sensitive JS/TS code.
Find relevant PR reviewers based on code ownership and recency of contributions. Use when creating PRs or needing to identify who should review code changes.
Guides bug report and pull request investigation and reproduction. Confirms reported behavior is wrong, reproduces issues locally, and checks for correct-by-design behavior before writing fixes. Use when given a bug report, issue, or error report to investigate.