s-audit
Audits World of Warcraft addons for security, technical debt, and deprecation compliance.
Install
mkdir -p .claude/skills/s-audit && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9633" && unzip -o skill.zip -d .claude/skills/s-audit && rm skill.zipInstalls to .claude/skills/s-audit
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Comprehensive quality analysis for WoW addons. Combines security, complexity, deprecation, and dead code analysis into a single audit workflow. Triggers: audit, quality, analysis, review, check, scan.Key capabilities
- →Scan for security vulnerabilities like unsafe eval
- →Analyze code complexity and nesting levels
- →Identify deprecated WoW APIs
- →Detect dead code and orphaned files
How it works
The skill executes specific MCP tools to perform multi-layered static analysis on addon code against security and maintainability standards.
Inputs & outputs
When to use s-audit
- →Scan addon for deprecated APIs
- →Perform security audit for taint risks
- →Analyze code complexity
- →Identify and remove dead code
- →Validate addon against 12.0 standards
About this skill
Auditing WoW Addons
Expert guidance for comprehensive addon quality analysis.
Related Commands
- c-audit - Full audit workflow
- c-clean - Dead code cleanup
- c-lint - Syntax and style
- c-review - Full review (includes audit)
MCP Tools
| Task | MCP Tool |
|---|---|
| Security Analysis | addon.security(addon="MyAddon") |
| Complexity Analysis | addon.complexity(addon="MyAddon") |
| Deprecation Scan | addon.deprecations(addon="MyAddon") |
| Dead Code Detection | addon.deadcode(addon="MyAddon") |
Capabilities
- Security Analysis — Combat lockdown, secret values, taint, unsafe eval
- Complexity Analysis — Deep nesting, long functions, magic numbers, duplicates
- Deprecation Scanning — 100+ deprecated APIs with migration paths
- Dead Code Detection — Unused functions, orphaned files, dead exports
Analysis Categories
Security (addon.security)
| Category | Description | Severity |
|---|---|---|
combat_violation | Protected API without InCombatLockdown() guard | Error |
secret_leak | Logging/storing secret values (12.0+) | Error |
taint_risk | Unsafe global modifications | Warning |
unsafe_eval | loadstring/RunScript with variable input | Warning |
addon_comm | Unvalidated message parsing | Info |
Complexity (addon.complexity)
| Category | Threshold | Description |
|---|---|---|
deep_nesting | > 5 levels | Excessive if/for/while nesting |
long_function | > 100 lines | Functions too long to understand |
long_file | > 500 lines | Files that should be split |
magic_number | pattern-based | Unexplained numeric literals |
duplicate_code | > 10 lines | Near-identical code blocks |
Deprecations (addon.deprecations)
| Category | Example APIs | Since |
|---|---|---|
addons | GetAddOnInfo → C_AddOns.GetAddOnInfo | 11.0 |
spells | GetSpellInfo → C_Spell.GetSpellInfo | 11.0 |
items | GetItemInfo → C_Item.GetItemInfo | 11.0 |
containers | GetContainerItemInfo → C_Container | 10.0 |
unit | UnitHealth (returns secret for enemies) | 12.0 |
Dead Code (addon.deadcode)
| Category | Description |
|---|---|
unused_function | Functions defined but never called |
orphaned_file | Lua files not in TOC |
dead_export | Exported values never used |
unused_library | Libraries in Libs/ never used |
Workflow
Quick Audit
1. addon.security → Critical issues (combat, secrets)
2. addon.deprecations (min_severity=error) → Breaking changes
3. Report critical findings
Full Audit
1. addon.security → All security issues
2. addon.complexity → All maintainability issues
3. addon.deprecations → All deprecated APIs
4. addon.deadcode → All dead code
5. Comprehensive report with priority order
Interpreting Results
Priority Order
-
Critical (Fix immediately):
- Combat lockdown violations (will cause bugs)
- Secret value leaks (12.0+ breaking)
- Deprecated APIs with
severity: error
-
High (Fix before release):
- Taint risks
- Deprecated APIs with
severity: warning - Orphaned files
-
Medium (Fix when convenient):
- Deep nesting (maintainability)
- Long functions
- Magic numbers
-
Low (Consider fixing):
- Code duplicates
- Suspicious dead code
Best Practices
- Run before release — Catch breaking changes early
- Start with critical — Security and deprecations first
- Filter by severity — Use
include_suspicious=falsefor focused results - Check 12.0 readiness — Secret value APIs are breaking changes
- Review complexity — High complexity = high bug risk
When not to use it
- →When auditing non-WoW addon code
- →When environment lacks access to addon files
Limitations
- →Limited to static code analysis
How it compares
It automates the detection of WoW-specific deprecations and combat lockdown risks, which manual review might miss.
Compared to similar skills
s-audit side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| s-audit (this skill) | 0 | 7mo | No flags | Advanced |
| github-code-review | 13 | 2mo | Review | Advanced |
| reviewing-code | 21 | 8mo | No flags | Intermediate |
| reviewing-nextjs-16-patterns | 11 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Falkicon
View all by Falkicon →You might also like
github-code-review
ruvnet
Comprehensive GitHub code review with AI-powered swarm coordination
reviewing-code
CaptainCrouton89
Systematically evaluate code changes for security, correctness, performance, and spec alignment. Use when reviewing PRs, assessing code quality, or verifying implementation against requirements.
reviewing-nextjs-16-patterns
djankies
Review code for Next.js 16 compliance - security patterns, caching, breaking changes. Use when reviewing Next.js code, preparing for migration, or auditing for violations.
cookbook-audit
anthropics
Audit an Anthropic Cookbook notebook based on a rubric. Use whenever a notebook review or audit is requested.
pr-review
pytorch
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
find-bugs
davila7
Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.