auditlisted

Comprehensive codebase audit skill covering 10 systemic bug categories plus CI automation. Use this skill proactively during code review, E2E testing, pre-deployment checks, or whenever you spot any of these patterns — raw database values in UI (snake_case, camelCase enums, numeric codes), API contract mismatches between client and server, Firestore/database rules gaps, CORS missing production domains, analytics/consent gating features, dynamic Tailwind/CSS classes purged in prod, window.open without noopener, orphaned data on deletion, hardcoded secrets, Android/iOS security misconfigs, performance regressions (bundle size, re-renders, lazy loading), or accessibility gaps (missing aria labels, keyboard nav, screen reader). Also triggers on "audit this", "did you check everything", "is this production ready", "what did we miss", "are you sure", or any thoroughness question. One bug instance always means many more exist — this skill enforces the ripple search.
aksheyw/claude-code-learned-skills · ★ 0 · DevOps & Infrastructure · score 72

Install: claude install-skill aksheyw/claude-code-learned-skills

# Codebase Audit — 10-Category Systemic Bug Finder This skill codifies hard-won lessons from production bugs. Every pattern here was discovered the hard way — usually one instance revealing many more across the codebase. Use it proactively, not reactively. ## How to Use This Skill Pick the relevant audit category (or run all 10 for a pre-deploy check). Each category has: - **Why it matters** — the real-world consequence - **Detection** — how to find instances - **The ripple search** — how one bug leads to more - **Fix pattern** — the proven solution - **Checklist** — verify completeness --- ## 1. Display Value Formatting **The bug:** Database/API values stored as machine-readable keys (`bright_indirect`, `cactus_mix`, `glazed_ceramic`) leak into the UI without formatting. **Why it's systemic:** The same field renders in multiple views (detail pages, cards, lists, settings). If one field leaks raw values, sibling fields almost certainly do too. In the original case, one `bright_indirect` bug turned into 9 fixes across 7 files. ### Detection Scan for template expressions that render data fields without a formatting function: ``` # Red flags in rendered output: {plant?.fieldName} # React/JSX — raw field in display context {{ item.field_name }} # Vue/Angular/Handlebars ${data.fieldName} # Template literals ``` **Visual red flags:** - Underscores in user-facing text (`bright_indirect`, `cactus_mix`) - camelCase in user-facing text (`needsAtte