blade-audit

Auditing BladeX code for security and architecture issues involves inspecting the target module to detect auth gaps, transaction bugs, and framework violations. This Skill performs a six-dimension review in one pass, generating a severity-ranked Markdown report with file and line references.

Yes, you can review specific BladeX git commits instead of the full codebase. The Skill supports commit-range analysis to verify recent changes, allowing you to target specific updates rather than running a full-directory inspection.

Validating BladeX refactoring against design documents is done through design-vs-implementation comparison. The Skill checks if the updated code aligns with your original design, catching logic and framework compliance issues while producing repair guidance.

The BladeX code review covers performance regressions and data leaks directly. It applies six-dimension auditing rules to robustness and performance, catching data exposure risks and generating prioritized findings with actionable repair steps.

To get a structured report from a full-directory BladeX codebase inspection, run the Skill on the target module. It produces a structured Markdown report containing severity-ranked findings, precise file and line references, and specific repair guidance.

The BladeX code audit checks for framework compliance conventions to ensure your codebase adheres to BladeX standards. It inspects the code against framework rules, returning prioritized findings that highlight violations and provide repair guidance.