Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Security

ln-22-codebase-auditor

Audits cross-cutting code health across security, delivery, maintainability, dependencies, diagnosability, concurrency, and lifecycle. Use when no specialist audit is primary.

levnikolaevich · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add levnikolaevich/claude-code-skills --skill ln-22-codebase-auditor

About this skill


name: ln-22-codebase-auditor description: "Audits cross-cutting code health across security, delivery, maintainability, dependencies, diagnosability, concurrency, and lifecycle. Use when no specialist audit is primary."

Codebase Auditor

Goal: Perform a broad, read-only production-code health audit. Find concrete cross-cutting failure, security, delivery, and maintenance risks without turning detector matches or personal style preferences into findings. Do not substitute for documentation trust, test-portfolio, whole-architecture, or persistence-specific review.

Execution contract: Treat the ordered checkbox workflow below as this skill's Definition of Done. Track every checkbox as PENDING, then resolve it to PROVEN with concrete evidence, CLEARED with evidence that its conditional trigger is absent, or UNPROVEN; reading, mentioning, delegating, skipping, or tool failure is not proof. Before returning, resolve every PENDING, count only PROVEN and CLEARED items as complete, apply this skill's verdict, decision, and approval rules to every UNPROVEN, and prepend Checklist: X/Y completeIncomplete: None | section/item — reason; outcome impact; exact next action; list every UNPROVEN item.

Tool Routing

NeedPreferred toolUse it whenFallback
Repository map and stack detectionNative file listing, manifests, build files, and repository instructionsEstablishing scope, generated areas, entrypoints, supported runtimes, and commandsTargeted tree inspection and known entrypoints
Symbols, callers, ownership, and data flowLanguage server or host-native code intelligenceA finding depends on symbol identity, references, overrides, route wiring, or cross-file behaviorNarrow text search plus direct inspection of every relevant match
Current changes and historical contextGit status, diff, log, and blameSeparating current work, regressions, intentional constraints, and dead compatibility pathsCurrent implementation and explicit decision records
Delivery healthRepository-defined build, lint, type, test, and smoke commandsEstablishing whether the project can ship in its documented environmentInspect CI and scripts; mark execution unavailable
Dependency and security stateNative package-manager audit, manifests, lockfiles, and official advisoriesChecking known vulnerabilities, unsupported versions, and dependency healthOfficial registry and vendor sources; never guess severity
Runtime evidenceExisting logs, metrics, traces, profiles, and diagnosticsStatic analysis cannot establish frequency, reachability, or operational impactCall-path analysis with an explicit static-only limitation
Current external behaviorOfficial specifications, vendor documentation, and release notesA finding depends on current API, runtime, or standard behaviorPrimary-source web research; otherwise mark UNVERIFIED

Start with summary-level discovery and narrow before reading deeply. Run only repository-defined or clearly safe diagnostic commands; never publish, deploy, migrate production data, rotate secrets, or rewrite files during the audit.

Evidence Rules

  • A pattern match is a candidate, not a finding. Confirm reachability, context, and consequence.
  • Runtime failure or deterministic command output outweighs static suspicion; static evidence remains valid when execution is unavailable and the limitation is explicit.
  • Generated, vendored, fixture, migration-history, and intentionally compatible code require context-specific treatment.
  • External best practice is actionable only when it addresses a concrete repository defect or risk.
  • Score or count only findings with distinct root causes; deduplicate symptoms that share one correction.

Checklist

1. Establish Scope and Baseline

  • Detect languages, frameworks, package managers, entrypoints, deployment model, generated areas, and the repository's supported verification commands.
  • Classify each runtime surface as long-running service, CLI, library, job, serverless function, or platform-managed component before requiring probes, telemetry, signal handling, or shutdown behavior.
  • Read applicable instructions and identify security boundaries, critical business paths, public interfaces, and irreversible operations.
  • Inspect Git state so the audit does not overwrite, misattribute, or ignore unrelated user changes.
  • Establish build, lint, type, test, and smoke baseline where feasible; record commands, environment, exit status, and relevant output.
  • Define exclusions and depth based on risk rather than scanning every file with equal effort.
  • Keep the audit read-only. Allow only permitted caches and build artifacts and disclose them when created.

2. Audit Security and Delivery Boundaries

  • Search for committed secrets, unsafe credential patterns, sensitive defaults, debug bypasses, and accidental exposure through logs or errors.
  • For credential findings, never expose the raw value: distinguish live material from placeholders, fixtures, examples, and allowlisted fingerprints; report only the type, location, and redacted evidence, and recommend revocation, rotation, or history remediation only for confirmed exposure without performing it during the audit.
  • Trace untrusted input into SQL, shell, templates, HTML, file paths, URLs, deserialization, redirects, and other injection-sensitive sinks.
  • Check authentication, authorization, tenant or ownership isolation, privilege transitions, insecure direct object access, and default-deny behavior.
  • Check validation at trust boundaries, canonicalization, size and rate limits, unsafe file operations, and destructive-action confirmation or guards.
  • Verify security findings against actual call paths, framework behavior, configuration, and current official guidance before assigning severity.
  • Inspect
Read the complete source ↗