Audit Domain 13 Code Integrity
Audit code integrity and coherence — duplication, hallucinated references, Tambon signatures, spec drift, Frankenstein patterns, mystery code. THIS DOMAIN incorporates findings from the Tambon hunt and blind spots B9, B12, B13, B14. Run as part of /audit Phase E.
Install
npx skills add wolverin0/claude-skills --skill audit-domain-13-code-integritygit clone --depth 1 https://github.com/wolverin0/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/audit/audit-domain-13-code-integrity ~/.claude/skills/audit-domain-13-code-integrityPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Skill: Audit Domain 13 — Code Integrity & Coherence (LLM-failure-mode domain) This skill audits one specific domain. It runs in an isolated subagent context spawned by the audit-orchestrator. The subagent loads this skill and the audit rules, runs against the audit scope, and returns a ~2K-token findings report. ## Pre-flight ``` view ~/.codex/context/audit-rules.md ``` If you have findings from previous audit phases (hard stops, Tambon, blind spots), the orchestrator passes them as input. Use them — don't re-discover findings other phases already produced. Specifically: - Hard stops related to this domain: H9 - Blind spots that route to this domain: B9, B12, B13, B14 If the orchestrator didn't pass you these inputs, do NOT re-run the hard-stops or blind-spots walks. Audit your domain only and trust the orchestrator to stitch. ## Scope Duplication (Type-1 through Type-4 clones), hallucinated references, Tambon signatures (already counted in Phase C), spec-vs-code drift, Frankenstein patterns (multiple HTTP clients, multiple state libs), mystery code (unowned, unreferenced), test-mirrors-code patterns. ## Key questions to answer For each, find the evidence and report it. The questions are the audit's spine — every finding maps back to one of them. 1. Tambon density: take the figure from the Phase C hunt (audit-tambon-hunt); do not recount (see the rollup below). 2. Are there duplicate functions / endpoints / utilities?
Details
- Skill name
audit-domain-13-code-integrity- Repository
- wolverin0/claude-skills
- Path
skills/audit/audit-domain-13-code-integrity/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Audit Domain 13 Code Integrity skill do?
Audit code integrity and coherence — duplication, hallucinated references, Tambon signatures, spec drift, Frankenstein patterns, mystery code. THIS DOMAIN incorporates findings from the Tambon hunt and blind spots B9, B12, B13, B14. Run as part of /audit Phase E.
How do I install the Audit Domain 13 Code Integrity skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill audit-domain-13-code-integrity. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Audit Domain 13 Code Integrity popular?
It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.
Related skills
UI UX Pro Max
41wolverin0/claude-skills
UI/UX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, and HTML/CSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism,
Audit Blind Spots
41wolverin0/claude-skills
Walk the B1-B19 AI-to-AI blind-spot catalog systematically. Use during the audit pipeline AFTER hard-stops and Tambon hunt and BEFORE the 13 domain audits. Output: PRESENT / NOT PRESENT for each B-class with evidence. Findings flow into the appropriate domains.
Audit Decisions
41wolverin0/claude-skills
Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.
Audit Method
41wolverin0/claude-skills
Run the methodology setup phase of a technical audit — fingerprint the stack, inventory the repository, and produce a system map. Use this BEFORE running any audit domains. Output: detected stack, repo summary, and high-level architecture in 3-5 paragraphs. No findings yet.
Audit Domain 02 Architecture
41wolverin0/claude-skills
Audit the architecture and code quality domain — module boundaries, abstraction layers, code organization, naming, documentation. Run as part of /audit Phase E.
Audit Orchestrator
41wolverin0/claude-skills
Conduct a full technical due diligence audit of a vibe-coded codebase. Use when the user types `/audit`, asks for a "full audit," asks for a "due diligence review," asks "is this codebase ready to ship?", or asks for a comprehensive code review of an entire repository (not a single PR). Coordinates the 13 domain skills, the hard-stop hunt, the Tambon LLM-signature hunt, and the blind-spot walk. Produces a single dual-layer report (founder view + technical evidence).
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.