Audit CaseDive codebase for API security, test coverage, and performance issues.
npx skills add https://github.com/alasdairnc/casedive --skill casedive-audit
Please help me install this Agent Skill. Skill: casedive-audit Source: https://github.com/alasdairnc/casedive/tree/main/.claude/skills/casedive-audit Command: npx skills add https://github.com/alasdairnc/casedive --skill casedive-audit
This Skill helps CaseDive teams maintain high code quality and security posture by automatically auditing the codebase and recording results in a persistent append-only log to surface trends over time.
Run the audit to append findings to AUDIT_LOG.md without modifying source code.
High-intent search queries and answers about installing and using this skill.
You can audit codebase security and test coverage by running an automated scan that surfaces API risks, config hygiene, and performance issues. The audit appends findings to an AUDIT_LOG.md file without modifying source code, providing a pre-flight health snapshot for deployment readiness.
An append-only audit log is a persistent record where each codebase audit run adds findings without overwriting history. This mechanism tracks code health trends by comparing current findings against prior entries to surface what is new, still open, or fixed.
Yes, you can compare current audit findings against previous runs. The audit process diffs current results against historical entries in the log, surfacing new regressions, still-open risks, and fixed issues across API security, data quality, and performance metrics.
No, the codebase audit process does not modify your source code. It scans for API security, test coverage, legal data quality, config hygiene, and performance issues in read-only mode, ensuring all findings are recorded only in the audit log file.
The best way to maintain code quality during periodic health checks is to run an automated audit that scans security, coverage, and config hygiene. Using phase-based exploration guidelines, it appends results to a persistent log to surface risk trends over time.
You should run a code health audit before deployment to quickly identify regressions and risk areas across API security and performance. It provides a team readiness snapshot by appending findings to an audit log without altering code.
goofansuSync GitHub issues with local Markdown files for offline editing.
proffesor-for-testingGenerate and index test reporting analytics for QE metrics in CI/CD pipelines.
Ramprasad4121Prepare codebases for security review with static analysis and documentation.
AngelP17Automate CI/CD pipelines, infrastructure provisioning, and deployments across AWS, GCP, and Azure.
