audit

Detects dead code, unused endpoints, and semantic API discrepancies through static analysis.

1|Updated Jul 18, 2025
One-click install
npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill audit-adelysalberto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/AdelysAlberto/md-configs-and-agents/tree/main/agents-antigravity/config/skills/audit
Command: npx skills add https://github.com/AdelysAlberto/md-configs-and-agents --skill audit-adelysalberto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate dead code, orphaned endpoints, and semantic mismatches between API definitions and implementations over time, making maintenance risky and refactoring dangerous. ## Core Features & Use Cases - Dead Code Detection: Identifies unused functions, classes, and modules that can be safely removed. - Unused Endpoint Discovery: Finds API endpoints that are defined but never called by any client or internal consumer. - Semantic API Audit: Flags discrepancies between API contracts and their actual implementations. - Use Case: Before a major refactor, run a static audit to list all dead code paths and unused endpoints so the team can delete them confidently instead of migrating obsolete logic. ## Quick Start Ask the agent to audit this repository for dead code, unused endpoints, and API semantic discrepancies.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I find dead code in my codebase?▼

Invoke the audit skill on your repository to statically analyze the source and list unused functions, classes, and modules. It reports candidates for removal so you can review them before deleting anything.

How to detect unused API endpoints in a project?▼

The audit skill scans endpoint definitions and cross-references them against call sites to identify endpoints with no consumers. This helps you retire obsolete routes before a refactor or API version migration.

What is a semantic API discrepancy?▼

A semantic discrepancy occurs when an API's documented or declared contract does not match its actual implementation behavior. The audit flags these mismatches so documentation and code stay consistent.

Does the audit skill modify or delete code automatically?▼

No, it performs read-only static analysis and reports findings. Deletion or refactoring decisions remain with the developer after reviewing the audit output.

When should I run a code hygiene audit?▼

Run it before major refactors, framework upgrades, or API version changes. It is also useful periodically on long-lived codebases where dead code and orphaned endpoints accumulate over time.