mcpField
S
sniper-check

sniper-check

github.com/fusengineTesting & quality3440 installsUpdated 2w ago
Repository

About sniper-check

Sniper Check is a skill that runs a code-quality workflow in an isolated context, for validation after code changes. It performs impact analysis, lint checks, minimal fixes, and re-verification, returning only the final validation report to the parent conversation.

Key features

  1. 01Run checks in an isolated context
  2. 02Six-phase code-quality workflow
  3. 03Grep-based usage impact analysis
  4. 04Lint error detection and fixes
  5. 05Re-verify until zero errors
  6. 06Return only the final report

Use cases

  1. 01Check code quality after modifications
  2. 02Validate a specific file or directory
  3. 03Run project checks after refactoring
  4. 04Find and fix lint errors

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fusengine/claude-plugins --skill sniper-check

After installing, type/sniper-checkin Claude Code to confirm it loaded.

Details

From the project README
Sniper Check runs the full sniper agent 6-phase code-quality workflow (parallel explore-codebase + research-expert, Grep-based impact analysis, linter error detection, minimal correction, re-verification to zero errors) in an isolated forked context, so only the final validation report returns to the parent conversation -- nothing of the investigation itself pollutes it. Use it after any code modification, on a specific file, a directory, or the whole project.

Target: $ARGUMENTS

Sniper Check

Overview

Quick code quality validation using the sniper agent in an isolated forked context. Executes the full 6-phase workflow without polluting the main conversation context.

FeatureDetail
ContextForked (isolated sub-agent)
Agentsniper (Sonnet)
Phases6-phase code-quality workflow
ResultOnly final report returns to parent

When to Use

ScenarioUse
After code modifications/sniper-check src/
Validate specific file/sniper-check path/to/file.ts
Full project check/sniper-check .
After refactoring/sniper-check src/components/

Workflow

Execute the mandatory 6-phase code-quality workflow:

  1. PHASE 1+2 (PARALLEL): Launch both in parallel:
    • explore-codebase (Haiku) → Architecture discovery
    • research-expert (Sonnet) → Documentation verification
  2. PHASE 3: Grep all usages → Impact analysis
  3. PHASE 4: Run linters → Detect errors
  4. PHASE 5: Apply corrections → Minimal changes
  5. PHASE 6: Re-run linters → Zero errors

CRITICAL: Phases 1+2 must run in PARALLEL (two Task calls in one message).


Critical Rules

RuleReason
Never skip phases 1+2Documentation-backed fixes only
Always run phases in orderDependencies between phases
Zero linter errorsNon-negotiable exit criteria
Minimal changes onlySmallest fix necessary

Report Format

Return a validation report with:

  • Architecture summary (from explore-codebase)
  • Documentation references (from research-expert)
  • Impact analysis table (usages, risk level)
  • Errors fixed (critical, high, medium, low)
  • SOLID compliance status
  • Final linter status (must be ZERO errors)

Comments

Markdown supported