deep-audit

Audit the Crispy CRM codebase for security, data integrity, and quality gaps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/krwhynot/crispy-crm --skill deep-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deep-audit
Source: https://github.com/krwhynot/crispy-crm/tree/main/.claude/skills/deep-audit
Command: npx skills add https://github.com/krwhynot/crispy-crm --skill deep-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Comprehensive, phased audits of the Crispy CRM codebase across security, data integrity, code quality, UI/UX compliance, performance, testing, and documentation—delivering a unified view of risk and improvement areas.

Core Features & Use Cases

  • Phased audit methodology (Critical > Improvements > Polish) ensures critical issues are addressed first, with a consolidated MD report and generated todos.
  • Integrates engineering-constitution and ui-ux-design-principles into a single audit workflow.
  • Outputs are stored as markdown reports in docs/audits/*.md for traceability and handoff.

Quick Start

Trigger the audit on a codebase change or after major refactors with the deep-audit trigger to generate a full phased report.

Frequently Asked Questions about deep-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a codebase for security and quality issues?

Codebase audits systematically review code for security vulnerabilities, data integrity gaps, and quality problems across your stack. Trigger deep-audit on your Crispy CRM codebase to generate a phased report prioritizing critical issues first, then improvements and polish, with consolidated findings in markdown and auto-generated todos.

What gets flagged in a full-stack code audit?

Full-stack audits identify security flaws, data integrity risks, code quality gaps, UI/UX compliance violations, performance issues, testing gaps, and documentation deficiencies. Deep-audit integrates engineering-constitution and ui-ux-design-principles into a single workflow, producing a unified risk view.

When should I run a codebase audit?

Run audits after feature completion, post-refactor, before major releases, when onboarding to unfamiliar code areas, or when explicitly triggered via audit, deep-audit, quality-check, or code-review requests. Phased reporting ensures critical issues surface first.

How are audit results organized and stored?

Audit results are consolidated into markdown reports stored in docs/audits/*.md for traceability and team handoff. Reports follow phased methodology (Critical > Improvements > Polish) and include auto-generated actionable todos.

Can I audit specific areas or do I need a full codebase scan?

Deep-audit runs comprehensive full-stack analysis by default, covering security, data integrity, code quality, UI/UX, performance, testing, and documentation. The phased output lets you prioritize critical issues first regardless of scope.

What frameworks or codebases does deep-audit work with?

Deep-audit is built for the Crispy CRM codebase and integrates engineering-constitution and ui-ux-design-principles standards. It operates across explicit triggers (audit, deep-audit, codebase-audit, quality-check, code-review, /audit) and implicit lifecycle events.