Skip to content
Back to skills

Sniper Check

ASecurity

Use when validating code quality after modifications. Runs sniper agent in isolated forked context for clean, fast validation.

  • 29 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 28, 2026
ai-agentsgorefactoringdocumentation

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add fusengine/agents --skill sniper-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sniper Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sniper Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fusengine-sniper-check/badge)](https://www.skillsdirectory.com/skills/fusengine-sniper-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sniper-check
description: Use when validating code quality after modifications. Runs sniper agent in isolated forked context for clean, fast validation.
context: fork
agent: fuse-ai-pilot:sniper
user-invocable: true
argument-hint: "[file-or-directory]"
---

**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.

| Feature | Detail |
|---------|--------|
| **Context** | Forked (isolated sub-agent) |
| **Agent** | sniper (Sonnet) |
| **Phases** | 6-phase code-quality workflow |
| **Result** | Only final report returns to parent |

---

## When to Use

| Scenario | Use |
|----------|-----|
| 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

| Rule | Reason |
|------|--------|
| Never skip phases 1+2 | Documentation-backed fixes only |
| Always run phases in order | Dependencies between phases |
| Zero linter errors | Non-negotiable exit criteria |
| Minimal changes only | Smallest 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)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…