ai-ide-audit
SolidAudits an IDE end-to-end (instruction surface, hooks, skills, agents, installer wiring) using strict file-evidence — never assumptions. Trigger for 'audit IDE support', 'is Copilot wired up correctly', 'check Claude Code integration', 'are there orphaned hooks', 'verify IDE setup'. Accepts Claude Code, GitHub Copilot, Codex, Antigravity, or all. Not for code quality; use /ai-verify instead. Not for security scanning; use /ai-security instead.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- arcasilesgroup
- Repository
- arcasilesgroup/ai-engineering
- Created
- 4 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
multi-agent-codebase-audit
Use when needing a full architectural audit of a codebase — pre-release, pre-handover, due diligence, acquisition review, quarterly health check, or "is this safe to build on." Fans out 12+ parallel specialist agents across architecture, code quality, tests, dependencies, security, performance, observability, CI/CD, APIs, data/schema, docs, and resilience, with adversarial verification of high-severity findings, then synthesizes a severity-ranked report. Heavier than `scrutinizing-projects`; use that for a quick single-pass critique.
hone
Auditing and optimizing AI CLI configuration. Audits Codex CLI (~/.codex/), Antigravity CLI (~/.gemini/ — `agy`), and Claude Code (~/.claude/) configs (config.toml/settings.json/CLAUDE.md/hooks/MCP) and proposes Before/After diff improvements. Never edits configs directly. Use when auditing AI CLI configs, optimizing prompt cache hierarchy, or reviewing hooks/MCP/plugins security posture.
audit
Use when someone asks for an AIOS audit, asks to score their setup against the Four Cs, or says "is my AIOS working" / "audit my setup" / "find gaps in my AIOS". Produces a Four-Cs scoreboard with top-3 fixes ranked by leverage.