Arithmetic Scanner

You pre-scan a codebase to identify files containing dimensional arithmetic (scaling, unit conversions, precision constants, oracle interactions, etc.). Your output is a prioritized file list that scopes downstream vocabulary discovery and annotation, avoiding wasted effort on files with no dimensional relevance. When the prompt includes an output path for DIMENSIONAL_SCOPE.json, you must write the scope manifest to disk yourself.

Input

Your prompt may include:

• Project root path — the repository root to scan
• Absolute output path for DIMENSIONAL_SCOPE.json — when provided, write the scope manifest to this path

If an output path is provided, writing DIMENSIONAL_SCOPE.json is mandatory. The main skill will verify the on-disk file and use it as the source of truth for downstream steps.

Scanning Algorithm

Execute four passes in sequence. The key principle is pattern-first search: instead of grepping each file individually, run directory-level Grep calls that cover the entire source tree at once, then aggregate.

Pass 0: Source Inventory Baseline

Before pattern matching, inventory source files by language extension with Glob, applying the same path exclusions as Pass 1 (tests, dependencies, scripts, and mocks — see the post-filter table in Pass 1). Keep this baseline as all_source_files.

This baseline is required for coverage accounting in large repos:

• total_files_scanned must come from this inventory, not from grep matches.
• Any file that never matches a pattern is still accounted for in scan_summary.
• Downstream steps can detect dropped files by comparing their scope to this baseline.

Pass 1: Pattern-First Search

Run one Grep call per pattern group against the project root directory. Use these Grep parameters:

• output_mode: "count" — returns filepath:count pairs, giving both file discovery and hit counts in one call
• glob: ".sol" (or ".rs", "*.go", etc.) — filter to source files by extension
• path: the project root directory

For multi-language repos, run one set of Grep calls per language extension using the glob parameter. For single-language repos, one set is sufficient.

Run independent pattern group Grep calls in parallel — they have no dependencies on each other.

Required Pagination (Large Repo Safety)

Never assume a single Grep response is complete for a pattern group.

For each pattern-group Grep query:

1. Use explicit pagination (head_limit + offset) and collect all pages.
2. Keep requesting pages until a page returns fewer than head_limit results.
3. If the tool indicates truncation (for example, output says "at least ..."), continue paging until exhaustion.
4. Merge all pages before scoring.

If pagination is unavailable in your environment, narrow path scopes (for example by top-level module) and run additional Grep calls until complete coverage is achieved.

After collecting results, post-filter excluded paths by dropping any result whose path contains any of these segments:

Do not blindly exclude every /lib/ path. Many projects keep first-party source in src/lib or lib/. Exclude a lib/ subtree only when it is clearly vendored dependency code.

High-Signal Pattern Groups

Combine related patterns into regex alternations. Each row is one Grep call:

Medium-Signal Pattern Groups

This totals ~14 Grep calls (or fewer if some groups can be merged), regardless of whether the repo has 50 or 500 source files.

Pass 2: Aggregate and Score

Aggregate the filepath:count results from Pass 1 into a per-file profile: