loc-guardian

Initialize loc-guardian for this project — set LOC limit and extraction rules.

Count LOC, enforce per-file limits, get optimization strategies.

Use this agent to count lines of code and produce LOC statistics reports with file size limit enforcement. <example> Context: User wants to see code metrics for their project. user: "/loc-guardian:scan" assistant: "I'll use the counter agent to count lines of code." <commentary> Standard scan request — count all languages in the current directory. </commentary> </example> <example> Context: User wants LOC for a specific language. user: "/loc-guardian:scan python" assistant: "I'll use the counter agent to count Python lines of code." <commentary> Language-filtered scan — only count Python files. </commentary> </example>

Use this agent to analyze over-limit files and provide concrete optimization strategies. This agent is called by the scan command when files exceed the pure LOC limit. It reads the actual file contents and suggests specific extractions. <example> Context: counter found files over the LOC limit. assistant: "I'll use the optimizer agent to analyze the over-limit files and suggest optimizations." <commentary> The counter flagged violations. The optimizer reads each file and provides line-level extraction suggestions. </commentary> </example> <example> Context: counter's loc-data block contains only WARN lines (no OVER lines) — files are in the 80%+ warning zone but none have exceeded the limit. assistant: "No files are over the limit, but some are in the warning zone. I'll run the lighter warning-zone analysis — reading each WARN file and noting one obvious extraction candidate per file to prevent it from going over." <commentary> No OVER files — optimizer runs lighter WARN-only pass per the documented workflow. Per Step 3, each warning-zone file gets a single-line suggestion with one extraction candidate, rather than the full extraction + optimization report reserved for over-limit files. </commentary> </example>

Use when analyzing files that exceed pure LOC limits, or when suggesting code optimization opportunities to reduce file size.

Use when counting lines of code, computing LOC metrics, or formatting LOC reports with tokei.