scan
Scan Skill
Overview
Deterministic check engine that runs grep patterns and structural analysis against backend code. Accepts a scope argument (file path, directory path, or cwd) and a dimensions argument (comma-separated dimension list or "all") to control which checks execute.
This skill performs purely mechanical detection — it matches known patterns, counts structural violations, and reports findings with exact file locations. It does not make qualitative judgments about architecture or design. Other skills (like axiom:critique) handle subjective assessment and invoke scan when they need deterministic evidence.
See @skills/scan/references/check-catalog.md for scan-specific execution guidance including ordering, batching, and exclusions.
Triggers
Activate this skill when:
- User says "scan code", "check patterns", "run checks", or "detect anti-patterns"
- User runs
/axiom:scan - Another axiom skill requests deterministic pattern detection
- User wants mechanical verification of known code smells
Do not activate this skill when:
More from lvlup-sw/axiom
humanize
Scan for AI writing patterns in markdown, docs, comments, and user-facing strings. Detects 24 cataloged AI-writing tells across content, language, style, communication, and filler categories. Triggers: 'check prose', 'AI writing', 'humanize', or /axiom:humanize. Do NOT use for code quality — use other axiom skills.
1verify
Validate test quality by finding test-production divergence, mock overuse, and schema drift. Use when evaluating test suite health or after discovering a bug that tests missed. Triggers: 'check tests', 'test quality', 'verify contracts', or /axiom:verify. Do NOT use for architecture review — use axiom:critique instead.
1distill
Strip backend code to its essence by identifying dead code, vestigial patterns, and unnecessary complexity. Use when cleaning up after refactoring or reducing cognitive load. Triggers: 'simplify code', 'find dead code', 'clean up', or /axiom:distill. Do NOT use for error handling — use axiom:harden instead.
1harden
Strengthen backend resilience by finding silent catches, missing error context, resource leaks, and operational fragility. Use when hardening error handling or preparing for production deployment. Triggers: 'harden code', 'check error handling', 'resilience review', or /axiom:harden. Do NOT use for dead code — use axiom:distill instead.
1critique
Review backend architecture for SOLID violations, coupling issues, and dependency direction problems. Use when evaluating structural design decisions or preparing for refactoring. Triggers: 'review architecture', 'check SOLID', 'critique code', or /axiom:critique. Do NOT use for error handling — use axiom:harden instead.
1audit
Run a comprehensive backend quality audit across all eight dimensions. Orchestrates scan, critique, harden, distill, verify, and humanize skills, deduplicates findings, and produces a unified report with verdict. Use when assessing overall codebase health. Triggers: 'audit backend', 'full quality check', 'run audit', or /axiom:audit. Do NOT use for targeted checks — use individual skills instead.
1