Audit codebases for quality, security, performance, and architectural issues.
npx skills add https://github.com/cahyaong/ai.odin --skill audit-codebase
Please help me install this Agent Skill. Skill: audit-codebase Source: https://github.com/cahyaong/ai.odin/tree/main/.ai-toolbox/skills/audit-codebase Command: npx skills add https://github.com/cahyaong/ai.odin --skill audit-codebase
This Skill automates the process of auditing codebases for quality, security, performance, and architectural issues, saving time and reducing risk.
Run the audit workflow on your target project. The tool will select audit types, analyze the source directories, generate AUDIT_*.md in .ai-context, and apply the self-assessment protocol.
High-intent search queries and answers about installing and using this skill.
To automate a codebase audit, run the audit workflow to analyze source directories and identify quality, security, performance, and architectural issues. It generates severity-rated findings and structured AUDIT_*.md reports in the .ai-context folder.
A codebase audit report contains severity-based findings covering code quality, security vulnerabilities, performance bottlenecks, and architectural flaws. The tool generates these as AUDIT_*.md files and includes historical tracking with a self-assessment validation protocol.
Yes, you can audit a specific directory instead of an entire project. The codebase audit workflow supports applying deterministic analysis to targeted source directories, identifying issues and generating reports for that scope.
No external dependencies are required to run the automated codebase audit. The workflow operates independently to analyze repositories, select audit types, and produce severity-based markdown reports with self-assessment validation.
The self-assessment protocol validates codebase audit findings by applying a built-in verification process after generating the AUDIT_*.md reports. This ensures the accuracy of the severity-based findings regarding quality, security, performance, and architecture.
The best way to track codebase quality issues over time is by running the automated audit workflow, which supports historical tracking. It generates consistent AUDIT_*.md reports containing severity-based findings for ongoing comparison.
deepklarityScan codebases for misplaced files, dead code, temp files, and security/config slop; generate prioritized P0-P4 reports with guidance for P0-P2 items.
this-is-tobiAudit code repositories and generate prioritized REVIEW.md reports.
prof-danielcRun static analysis tools and aggregate results into a prioritized issue report.
saschadudkin-sketchIdentify security vulnerabilities in code and infrastructure and generate audit reports with severity ratings.
