sniper-check_skill

Overview

This skill runs a focused code-quality validation using the sniper agent in an isolated, forked context. It performs a mandatory 6-phase workflow to find, analyze, and fix issues while keeping the main conversation context clean. The final output is a concise validation report returned to the parent process.

How this skill works

The skill forks an isolated sub-agent that executes the six-phase code-quality workflow: parallel architecture discovery and documentation research, usage grep, linting, targeted fixes, and a final lint pass. Phases 1 and 2 run in parallel as two Task calls in one message to ensure documentation-backed fixes. Only the final validation report is sent back to the parent, preventing intermediate noise.

When to use it

• After making code modifications to validate changes quickly
• When validating a specific file or directory before committing
• After refactoring to ensure no regressions or hidden usages remain
• For a full-project sanity check before release or merge
• When you need documentation-backed fixes and minimal code edits

Best practices

• Always run the skill after edits to guarantee zero linter errors before merge
• Point the skill at the smallest relevant path to reduce runtime and noise
• Do not interrupt the forked workflow; phases must run in order
• Review the impact analysis before accepting automated fixes
• Enforce minimal change principle: prefer targeted fixes only

Example use cases

• Validate a single file: /sniper-check path/to/file.ts to catch lint and usage issues
• Sanity-check a refactor: /sniper-check src/components/ to detect missed usages
• Full repository sweep: /sniper-check . before a release to ensure clean linters
• Pre-merge gate: integrate sniper-check as a CI step for code-quality validation