sniper-check
SolidUse when validating code quality after modifications. Runs sniper agent in isolated forked context for clean, fast validation.
AI & Automation 25 stars
4 forks Updated 6 days ago MIT
Install
Quality Score: 87/100
Stars 20%
Recency 20%
Frontmatter 20%
Documentation 15%
Issue Health 10%
License 10%
Description 5%
Skill Content
<objective>
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.
</objective>
**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 analysi...
Details
- Author
- fusengine
- Repository
- fusengine/agents
- Created
- 8 months ago
- Last Updated
- 6 days ago
- Language
- CSS
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
Code & Development Solid
code-quality
Use when validating code quality after modifications -- SOLID compliance, DRY duplication, linter errors, architecture violations. Do NOT use for functional verification (run verification FIRST, then code-quality).
25 Updated 6 days ago
fusengine AI & Automation Listed
code-check
Fast code hygiene validation (lints, formatters, tests, coverage) for quick development loop feedback.
38 Updated 4 days ago
rp1-run AI & Automation Solid
verification
Use when marking a task complete, finishing a feature, or claiming a bug fixed -- verifies functional resolution before closing. Do NOT use for lint/quality checks (use sniper AFTER this).
25 Updated 6 days ago
fusengine