Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Violation Sweep

ASecurity

Scans source and .claude/ files for anti-pattern violations, applies the top mechanical fixes, and reports pre/post counts.

2 stars
0 votes
0 copies
0 views
Added 10/6/2026
ai-agentsgobash

Works with

cli

Security Analysis

A100/100

Scanned 10/6/2026

$npx -y skills add e128/dotnet-reference --skill violation-sweep --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Violation Sweep?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Violation Sweep
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/e128-violation-sweep/badge)](https://www.skillsdirectory.com/skills/e128-violation-sweep)

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

Download with Pro
Files
SKILL.md
---
name: violation-sweep
description: >
  Scans source and .claude/ files for anti-pattern violations, applies the top
  mechanical fixes, and reports pre/post counts.
when_to_use: >
  violation sweep, sweep violations, fix violations, clean violations,
  sweep all violations, fix anti-patterns, sweep skills.
allowed-tools: Bash, Read, Edit, AskUserQuestion
argument-hint: "[--dry] [--claude]"
---

# Violation Sweep

Scan for anti-pattern violations, apply mechanical fixes, and report counts.

## Steps

### 1. Pre-fix scan

```bash
scripts/violation-scan.sh --json          # source (src/) only
scripts/violation-scan.sh --claude --json # also scan .claude/skills + .claude/agents
```

Pass `--claude` when the skill was invoked with `--claude`. Parse the JSON:
- `violations`: overall count
- `by_pattern`: object keyed by pattern name. Each has `{count, reason, files}`

Sort pattern entries by `count` descending. If `violations == 0`: emit
"No violations found." and stop: skip Steps 2-4.

### 2. Fix top mechanical categories (or --dry preview)

For the top 3 patterns by count, apply the fix described in each pattern's
`reason` field. These are mechanical, one-line substitutions:

| Pattern           | Fix                                                                 |
| ----------------- | ------------------------------------------------------------------- |
| `datetime-now`    | Inject `TimeProvider` via DI. Use `timeProvider.GetUtcNow()`        |
| `new-httpclient`  | Inject `IHttpClientFactory`. Use `factory.CreateClient()`           |
| `async-void`      | Change return type to `async Task` (except event handlers)          |
| `sync-over-async` | `await` the task instead of `.Result` / `.GetAwaiter().GetResult()` |

For each file in the pattern's `files` list: Read it, apply the fix with Edit.

**If `--dry` was passed:** report the files and intended fix per pattern, then
stop: skip Steps 3 and 4.

### 3. Post-fix scan (normal mode only)

Re-run the same scan command from Step 1 and capture the post-fix total.

### 4. Show the diff, then stage on confirmation (normal mode only)

Present the changed files before staging:

```bash
scripts/diff.sh --json
```

After the user confirms, stage:

```bash
scripts/internal/stage.sh --include-new
```

### 5. Report

Emit a summary table:

```
Violation Sweep

  Pre-fix total:    N violations
  Post-fix total:   N violations  (or: N/A — dry run)
  Categories fixed: pattern-name (N→M), pattern-name (N→M), ...
  Deferred:         pattern-name (needs human review), ...
```

## Rules

- **Stage only: do not commit**, caller handles the commit
- **Skip context-sensitive fixes**: event-handler `async void`, intentional
  `DateTime.Now` in tests, etc. Surface these in the "Deferred" row.
- **`--dry` skips writes and staging**: scan + preview only
- **Top 3 only**: cap fixes at 3 pattern categories per sweep to keep scope bounded
- **Re-Read before Edit after any format run**: a format pass invalidates prior reads

Attribution

e128e128
View sourceSee grades on GitHubMore from e128 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →