audit

Orchestrate codegraph-powered sub-skills to produce severity-ranked audit reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codegraph.

What problem does it solve?

Detecting code quality risks across a codebase is complex. The Audit skill orchestrates codegraph-driven sub-skills to identify stacks, map dependencies, and produce an evidence-based, severity-ranked findings report.

Core Features & Use Cases

  • Orchestrates codegraph-based analysis to detect stacks and route to the right sub-skills for findings.
  • Generates an evidence-based audit report with severity classification and cross-file correlation.
  • Supports Rust and React/TypeScript stacks through dedicated best-practises modules, and is extensible to other stacks.

Quick Start

Run the audit on your repository to generate a severity-ranked findings report.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I perform a code audit on a Rust and TypeScript monorepo?

Code audits on Rust and TypeScript monorepos are performed by orchestrating codegraph-driven sub-skills to map dependencies and produce an evidence-based, severity-ranked findings report.

What is evidence-based risk analysis for code quality?

Evidence-based risk analysis for code quality detects structural risks by loading codegraph data, performing deep reads, and cross-correlating findings across files to generate severity classifications.

Does codegraph support static analysis for React and TypeScript frontends?

Codegraph supports static analysis for React and TypeScript frontends by routing to dedicated best-practises modules to identify stacks and map dependencies for audit findings.

How do I identify cross-file correlations during a codebase audit?

Cross-file correlations during a codebase audit are identified by deep reading loaded codegraph data to cross-correlate structural findings and map dependency relationships.

Can I extend code quality audits to stacks beyond Rust and JavaScript?

Code quality audits can be extended to stacks beyond Rust and JavaScript because the orchestration logic is extensible to other stacks through dedicated best-practises modules.