Audit Domain 09 Maintainability

Audit the dev experience and maintainability — local setup, documentation, test quality, CI feedback time, debuggability. Run as part of /audit Phase E.

41 stars 1 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add wolverin0/claude-skills --skill audit-domain-09-maintainability
Manual install
git 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-09-maintainability ~/.claude/skills/audit-domain-09-maintainability

Personal 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 9 — Developer Experience & Maintainability

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 @.claude/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, B13, B14, B15

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

Local setup ease (README clarity, Docker compose, seed data), code documentation, test quality (not just coverage), CI feedback time, debuggability, onboarding time for new contributors.

## 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. Can a new developer run the app locally in <30 minutes from clone?
2. Are tests fast enough to run on every commit?
3. Do tests test behavior, not implementation?
4. Are there integration tests, or just unit tests with mocks?
5. Are public functions documented?
6. Is there a CONTRIBUTING.md or similar?
Read the full skill on GitHub

Details

Skill name
audit-domain-09-maintainability
Path
skills/audit/audit-domain-09-maintainability/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Audit Domain 09 Maintainability skill do?

Audit the dev experience and maintainability — local setup, documentation, test quality, CI feedback time, debuggability. Run as part of /audit Phase E.

How do I install the Audit Domain 09 Maintainability skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add wolverin0/claude-skills --skill audit-domain-09-maintainability. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Audit Domain 09 Maintainability popular?

It lives in wolverin0/claude-skills, which has 41 GitHub stars and 1 forks.

Related skills

UI UX Pro Max

41

wolverin0/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,

Frontend & Design

Audit Blind Spots

41

wolverin0/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.

AI, LLMs & Agents

Audit Decisions

41

wolverin0/claude-skills

Standardize remediation decisions, baseline-policy entries, and legal-review banners for accepted, deferred, or policy-blocked audit findings.

Marketing, Sales & Business

Audit Domain 11 Demo Vs Prod

41

wolverin0/claude-skills

Audit the gap between demo-quality and production-quality — hardcoded test data, dev-only configurations shipped, missing prod hardening. Run as part of /audit Phase E.

Testing & QA

Analyze Prime Numbers

45

pjt222/agent-almanac

Analyze prime numbers using primality tests, factorization algorithms, prime distribution analysis, and sieve methods. Covers trial division, Miller-Rabin, Sieve of Eratosthenes, and the Prime Number Theorem. Use when determining whether an integer is prime or composite, finding prime factorizations, counting or listing primes up to a bound, or investigating prime properties within a number-theoretic proof or computation.

Testing & QAIn 1 list

Autoqa

41

wolverin0/claude-skills

Self-QA a repo's running application end-to-end — discover how it runs, build a feature×modality test plan, execute it against a live instance, and produce a witnessed pass/fail report. Use when the user says "autoqa", "QA this repo/branch", "verify every feature works", "release readiness check", "test this like a QA engineer would", or another skill needs an automated QA pass before sign-off.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.