codebase-stability-audit

# Codebase Stability Audit Skill

This skill audits the **guardrails and tooling** around your code that ensure stability and prevent regressions. It doesn't check your code logic - it checks whether you have the infrastructure in place to catch bugs before they reach production.

## Why This Matters

"Vibe coding" projects often skip quality infrastructure:
- No tests = bugs discovered by users
- No pre-commit hooks = broken code gets committed
- No CI/CD = manual deployment mistakes
- No linting = inconsistent code, hidden bugs
- **Dead code accumulates** = bloated bundles, confusion

This audit identifies gaps in your quality infrastructure.

## Features

- **98+ stability checks** across 14 categories
- **Dependency architecture analysis** (circular deps, cross-feature imports)
- **Dead code detection with Knip** (unused files, exports, dependencies)
- **Test coverage analysis** (unit, integration, E2E)
- **ESLint configuration audit** (security rules, custom rules)
- **Pre-commit hooks check** (Husky, lint-staged)
- **CI/CD pipeline analysis** (GitHub Actions, GitLab CI)
- **TypeScript strictness audit**
- **Feature parity testing** detection
- **Custom compliance scripts** discovery

## Usage

```bash
/codebase-stability-audit:run         # Full audit
/codebase-stability-audit:run quick   # Quick check (2 min)
/codebase-stability-audit:run setup   # Generate missing configs
```

## Categories

### 1. Test Infrastructure (12 checks)

| Check | Description | Severity |
|-------|-------------|----------|
| Test framework present | Jest, Vitest, Mocha installed | CRITICAL |
| Test files exist | `*.test.ts`, `*.spec.ts` files found | CRITICAL |
| Test coverage configured | Coverage thresholds in config | HIGH |
| E2E tests present | Playwright, Cypress installed | HIGH |
| Integration tests | API/database tests exist | MEDIUM |
| Test scripts in package.json | `npm test` works | HIGH |
| CI runs tests | Tests in GitHub Actions | HIGH |
| Test utilities | Test helpe