AgentStack
SKILL verified MIT Self-run

Sniper Check

skill-fusengine-agents-sniper-check · by fusengine

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

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-fusengine-agents-sniper-check

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Sniper Check? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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
  1. PHASE 3: Grep all usages → Impact analysis
  2. PHASE 4: Run linters → Detect errors
  3. PHASE 5: Apply corrections → Minimal changes
  4. 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)

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.