snyk-vulnbench: Skill for Claude Code

cloc

Instructions

Estimate project size with cloc and report the result without modifying the project. Use the standard exclusions below so dependency folders, generated artifacts, documentation, configuration, and common metadata do not inflate the estimate.

Step 1: Resolve the directory

Accept one directory argument from the user's request.

1. If the argument is an existing directory, use it.
2. If the existing directory contains a direct project/ child and looks like a fixture root, use that child so findings.json and fixture-only assets are not counted.
3. Otherwise, if the argument is a fixture name, resolve it from the repository root as fixtures/<argument>/project.
4. If neither path exists, stop and ask the user for a valid directory or the exact fixture name. Do not guess from partial matches.

When the request names a fixture but the current directory is not the repository root, determine the repository root with git rev-parse --show-toplevel before resolving fixtures/.

Done when: you have one existing source directory and can report its resolved path.

Step 2: Verify prerequisites

Check that cloc is available with command -v cloc. If it is missing, report that clearly and let the user install it; do not install packages automatically.

Step 3: Run the standard count

Run this command recursively against the resolved directory. Preserve the exclusions unless the user explicitly asks to change them:

cloc \
  --exclude-ext=json,md,markdown,yml,yaml,svg \
  --exclude-lang=Dockerfile \
  --exclude-dir=.git,node_modules,dist,build,target \
  "<resolved-directory>"

Quote the directory path so names containing spaces work. Do not add --include-lang unless the user explicitly asks for only particular languages. Without that flag, cloc reports every recognized language remaining after the standard exclusions.

Done when: cloc exits successfully and produces its language summary.

Step 4: Report the estimate