s-audit_skill

Overview

This skill performs comprehensive quality analysis for World of Warcraft addons. It combines security checks, complexity metrics, deprecation scanning, and dead-code detection into a single audit workflow. The goal is to surface critical bugs, breaking API usage, and maintainability risks before release.

How this skill works

The skill runs modular checks: security rules detect combat lockdown, secret leaks, taint, and unsafe evals; complexity analysis measures nesting, function/file length, magic numbers, and code duplication; a deprecation scanner maps 100+ deprecated APIs to modern replacements; dead-code detection finds unused functions, orphaned files, and unused libraries. Results are prioritized (Critical → High → Medium → Low) and returned as a consolidated report with actionable items and suggested fixes.

When to use it

• Before publishing an addon release
• After upgrading to a new WoW client (major version)
• When CI indicates regressions or new warnings
• During pull requests for large refactors
• Before a public beta or stress test

Best practices

• Run a quick audit first to catch security and breaking deprecations
• Follow the priority order: fix Critical issues immediately
• Filter results by severity to focus the team (include_suspicious=false)
• Re-run audits after code removals to detect orphaned files
• Track complexity hotspots and split long files/functions proactively

Example use cases

• Pre-release check to eliminate combat lockdown and secret leaks
• Automated CI step that fails on Critical deprecations or security errors
• Code cleanup sprint guided by dead-code and duplicate detections
• Refactor validation to ensure no deprecated APIs remain after migration
• Maintainability review highlighting long functions and deep nesting hotspots