code-audit

Name: code-audit
Availability: InStock
Author: cinnamonfirj

Audit codebases for bugs, security vulnerabilities, and performance issues.

Updated Aug 27, 2026

Search Tags:#architecture #code review #performance #error handling #security audit #race condition #logic correctness

Ready to run

npx skills add https://github.com/CinnamonfirJ/task-hub-webapp --skill code-audit-cinnamonfirj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-audit
Source: https://github.com/CinnamonfirJ/task-hub-webapp/tree/main/skills/code-audit
Command: npx skills add https://github.com/CinnamonfirJ/task-hub-webapp --skill code-audit-cinnamonfirj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you systematically review code to uncover logic errors, race conditions, security vulnerabilities, performance issues, and architectural/code-smell problems before they reach production.

Core Features & Use Cases

Workflow-driven audits: Run a guided checklist across Logic & Correctness, Security, Performance & Resource Leaks, Architecture & Maintainability, and Error Handling & Edge Cases.
Scope flexibility: Audit the full codebase, a specific feature/module/folder, or a focused set of files for targeted change review.
Actionable severity-based output: Produce findings grouped by severity with clear “What/Why/Fix” guidance for remediation.

Quick Start

Use the code-audit skill to audit the folder containing the wallet feature and return a severity-grouped report of logic, security, performance, and edge-case issues.

Frequently Asked Questions about code-audit

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

FAQPage Schema

How do I find race conditions and security vulnerabilities in my codebase?▼

You can audit code by running a checklist-guided review that traces user flows, verifies async and type assumptions, validates boundary inputs, and checks authorization, producing a severity-grouped report with What/Why/Fix guidance.

What is the best way to review code for performance problems and maintainability smells?▼

The best way to review for performance and maintainability is running a structured code audit that evaluates resource cleanup and render/bundle efficiency, outputting severity-grouped findings with clear What/Why/Fix remediation guidance.

Can I run a security audit on just a single feature folder or specific pull request files?▼

Yes, code audits support scope flexibility, allowing you to target a single feature, module, folder, or specific pull-request files for focused checklist-guided reviews that output severity-grouped logic and security findings.

How does a code audit check for error handling and edge cases in async operations?▼

It checks error handling and edge cases in async operations by verifying async and type assumptions, validating boundary inputs, and reviewing resource cleanup, detecting race conditions and logic errors across the audited code scope.

Do I need to provide a full project to audit code for logic correctness and architecture issues?▼

No, you do not need a full project; you can audit selected files or a specific module to detect logic correctness and architecture issues, applying checklist-guided tracing and severity-based reporting to that scoped subset.