code-audit

Identify security vulnerabilities, code quality issues, and tech debt in full-stack repositories.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/get-caio/harness --skill code-audit-get-caio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/get-caio/harness/tree/main/.claude/skills/code-audit
Command: npx skills add https://github.com/get-caio/harness --skill code-audit-get-caio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security vulnerabilities, code quality issues, and tech debt in full-stack codebases can slip through phases and reviews, leading to late-stage fixes and risky releases.

Core Features & Use Cases

  • Post-phase validation during builds to surface issues early.
  • Final QA before external review to ensure code quality and security alignment.
  • Cold assessment of unfamiliar or inherited codebases to map risk and debt.
  • Configurable checks and guardrails to tailor the audit to project standards.

Quick Start

Run the code-audit skill after major phases or at build completion to generate a comprehensive security and quality report.

Frequently Asked Questions about code-audit

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

FAQPage Schema
How do I identify security vulnerabilities and tech debt in an inherited codebase?

You can identify security vulnerabilities and tech debt by running a cold assessment audit on the unfamiliar codebase, which surfaces actionable findings across architectures and provides reproducible reporting.

What is the best way to automate code quality and security checks during a build?

The best way to automate code quality and security checks during a build is to run post-phase validation, applying configurable guardrails via scripts to surface issues early before risky releases.

Can I configure code review guardrails to match my project standards?

Yes, you can configure code review guardrails to match your project standards by tailoring checks and project configurations, ensuring the static analysis and risk assessment align with your specific requirements.

Does static analysis work for full-stack repositories before external review?

Static analysis works for full-stack repositories by performing final QA before external review, ensuring code quality and security alignment through automated detection and reproducible reporting.

When should I run a risk assessment audit on my repository?

You should run a risk assessment audit after major development phases, at build completion, or during cold assessments of new codebases to surface security gaps and tech debt early.