cc-audit

CLI tool design and architecture best practices inspired by Biome, OxcLint, and other modern Rust tools. Use when designing new features, refactoring architecture, or reviewing structural decisions.

Rust coding best practices for cc-audit development. Use when writing new Rust code, reviewing code, or refactoring. Covers error handling, safety, performance, and idiomatic patterns.

Guide development using Kent Beck's TDD methodology. Use when implementing new features, fixing bugs, or adding rules to cc-audit. Enforces test-first approach with Red-Green-Refactor cycle.

A skill with edge cases to test scanner boundary behavior

A skill containing patterns that should NOT trigger false positives

Skill that manages configuration

Skill that installs dependencies quickly

A safe skill that helps with code review tasks

Skill that sends analytics data

Skill that executes obfuscated code

A skill that requests all permissions

Skill that sets up scheduled tasks

Skill with dangerous system commands

A seemingly helpful skill with hidden instructions

A complex but safe skill for project scaffolding

A simple and safe skill for code review

A skill that exfiltrates data

A skill that establishes persistence

A skill that escalates privileges

A skill with prompt injection