code-audit

Audit code for semantic flaws and generate a Markdown report with corrections.

3|1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Ilenburg1993/chatgpt-docker-puppeteer --skill code-audit-ilenburg1993
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/Ilenburg1993/chatgpt-docker-puppeteer/tree/main/.github/skills/code-audit
Command: npx skills add https://github.com/Ilenburg1993/chatgpt-docker-puppeteer --skill code-audit-ilenburg1993

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the limitations of automated tools by performing a deep, manual semantic audit of code to identify subtle bugs, logical flaws, and semantic gaps that static analysis tools often miss.

Core Features & Use Cases

  • Manual Semantic Audit: Identifies bugs, incompleteness, logical gaps, and semantic flaws missed by automated tools (ESLint, TypeScript, SonarQube, etc.).
  • Structured Reporting: Generates a Markdown report detailing findings, severity, evidence, and proposed corrections.
  • Upgrade Recommendations: Provides a second section with relevant upgrades to the existing code.
  • Use Case: A developer suspects a critical but hard-to-pinpoint bug in a core module. They use this Skill to get a thorough manual review, ensuring the code's correctness and identifying potential improvements.

Quick Start

Use the code-audit skill to perform a deep manual audit of the file '/src/utils/auth.js'.

Frequently Asked Questions about code-audit

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

FAQPage Schema
How do I find semantic bugs and logical flaws that automated static analysis tools miss?

Perform a manual semantic code audit to identify subtle bugs, logical gaps, and semantic flaws that automated tools miss. This approach reviews code semantics and structural correctness to pinpoint incompleteness that static analysis cannot reliably capture.

What is the best way to get structured upgrade recommendations for a specific code portion?

Conduct a deep code audit to generate a structured Markdown report with findings, severity, evidence, and correction proposals. The report includes a mandatory second section providing pertinent upgrade recommendations for the evaluated code scope.

How do I review code for technical debt and incompleteness in a specific module?

Specify the file or code portion to run a deep manual review evaluating technical debt and incompleteness. The audit produces a structured report with evidence and correction proposals, ensuring module correctness and identifying potential improvements.

Can I use a manual code review to evaluate structural improvements within a defined scope?

Yes, a manual semantic code audit evaluates structural improvements within a specified scope. It identifies logical gaps and semantic flaws, then outputs structured correction proposals and upgrade recommendations tailored to that code portion.

Does a manual semantic audit replace automated tools like SonarQube for bug detection?

No, a manual semantic audit complements automated bug detection tools by finding semantic flaws and logical gaps they often miss. It provides manual review, structured severity reporting, and upgrade suggestions that automated static analysis cannot reliably capture.