MCPInstall

ln-620-codebase-auditor

Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.

Installs
449
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-620-codebase-auditor
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads ln-620-codebase-auditor automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Paths: File paths (references/, ../ln-*) are relative to this skill directory.

Type: L2 Coordinator Category: 6XX Audit

Codebase Auditor

Mandatory Read

MANDATORY READ: Load references/evaluation_coordinator_runtime_contract.md, references/evaluation_summary_contract.md, references/evaluation_research_contract.md MANDATORY READ: Load references/audit_final_report_contract.md MANDATORY READ: Load references/codebase_audit_worker_boundaries.md MANDATORY READ: Load references/research_tool_fallback.md Conditional read: load references/epistemic_protocol.md only when source confidence or claim uncertainty affects issue validation.

Purpose

  • audit runtime/codebase risks: security, delivery gates, dependency/reuse health, maintainability, dead code, diagnosability, concurrency, lifecycle, and config validation
  • coordinate exactly ln-621 through ln-629
  • require stack-aware research before scoring

Runtime Contract

Runtime family:

  • evaluation-runtime

Identifier:

  • codebase-audit

Phase order:

  1. PHASE_0_CONFIG
  2. PHASE_1_DISCOVERY
  3. PHASE_2_RESEARCH
  4. PHASE_3_DELEGATE
  5. PHASE_4_AGGREGATE
  6. PHASE_5_REPORT
  7. PHASE_6_SELF_CHECK

Worker Set

  • ln-621-security-boundary-auditor
  • ln-622-build-delivery-gate-auditor
  • ln-623-duplication-overabstraction-auditor
  • ln-624-code-maintainability-hotspot-auditor
  • ln-625-dependency-reuse-auditor
  • ln-626-dead-code-pruning-auditor
  • ln-627-diagnosability-auditor
  • ln-628-concurrency-correctness-auditor
  • ln-629-runtime-lifecycle-config-auditor

Worker Invocation (MANDATORY)

Host Skill Invocation: Skill(skill: "...", args: "...") is mandatory delegation.

  • Claude: call the Skill tool exactly as shown.
  • Codex: if no Skill tool exists, locate the named skill in available skills, read its SKILL.md, treat args as $ARGUMENTS, execute that skill workflow, then return here with its result/artifact.
  • Do not inline worker logic or mark the worker complete without executing the target skill.

Use the Skill tool for delegated workers. Do not inline worker logic inside the coordinator.

TodoWrite format (mandatory):

  • Resolve audit scope and build manifest
  • Load codebase structure and stack
  • Run best-practice research
  • Delegate to domain audit workers
  • Aggregate worker findings
  • Generate final audit report and remediation plan
  • Verify cleanup and self-check

Representative invocations:

Skill(skill: "ln-621-security-boundary-auditor", args: "{scope}")
Skill(skill: "ln-622-build-delivery-gate-auditor", args: "{scope}")
Skill(skill: "ln-623-duplication-overabstraction-auditor", args: "{scope}")
Skill(skill: "ln-624-code-maintainability-hotspot-auditor", args: "{scope}")
Skill(skill: "ln-625-dependency-reuse-auditor", args: "{scope}")
Skill(skill: "ln-626-dead-code-pruning-auditor", args: "{scope}")
Skill(skill: "ln-627-diagnosability-auditor", args: "{scope}")
Skill(skill: "ln-628-concurrency-correctness-auditor", args: "{scope}")
Skill(skill: "ln-629-runtime-lifecycle-config-auditor", args: "{scope}")

Workflow

Phase 0: Config

Start evaluation-runtime with required_research=true.

Phase 1: Discovery

Detect project type, stack, and applicability of audit workers.

Phase 2: Research

Mandatory research sources:

  1. official docs or standards
  2. MCP Ref
  3. Context7 when framework docs matter
  4. current web best-practice research

Phase 3: Delegate

Delegate applicable audit workers. Child workers must use evaluation-worker-runtime and emit evaluation-compatible summaries.

Phase 4: Aggregate

Merge runtime/codebase risk findings using references/codebase_audit_worker_boundaries.md. Read every worker report_path, normalize actions, deduplicate repeated issues, resolve worker conflicts, and validate each actionable problem against the research source order in references/evaluation_research_contract.md.

Phase 5: Report

Write .hex-skills/runtime-artifacts/runs/{run_id}/audit-report/ln-620--final-report.md per references/audit_final_report_contract.md. Include the remediation plan, source-backed validation for each confirmed issue, and cleanup note. Remove temporary worker markdown reports after consolidation. The evaluation-coordinator summary report_path must point to the final report only.

Phase 6: Self-Check

Required checks:

  • research completed
  • all applicable worker summaries recorded
  • worker conflicts resolved with codebase_audit_worker_boundaries.md
  • aggregation completed
  • final remediation report written
  • cleanup verified
  • temporary worker markdown reports removed
  • coordinator summary recorded

Summary Contract

Write summary_kind=evaluation-coordinator.

Definition of Done

  • Evaluation runtime started
  • Applicable workers selected
  • Research completed
  • All applicable worker summaries recorded
  • Worker set remained exactly ln-621 through ln-629
  • Worker conflicts resolved with codebase_audit_worker_boundaries.md
  • Final report and remediation plan written
  • Temporary worker markdown reports removed
  • evaluation-coordinator summary written
  • Runtime completed

Meta-Analysis

Optional reference: load references/meta_analysis_protocol.md only when the user asks for post-run meta-analysis or protocol-formatted run reflection.

When requested after the coordinator run, analyze the session per protocol section 7 and include the protocol-formatted output with the final codebase audit result.

References

  • Workers: ../ln-621-security-boundary-auditor/SKILL.md, ../ln-622-build-delivery-gate-auditor/SKILL.md, ../ln-623-duplication-overabstraction-auditor/SKILL.md, ../ln-624-code-maintainability-hotspot-auditor/SKILL.md, ../ln-625-dependency-reuse-auditor/SKILL.md, ../ln-626-dead-code-pruning-auditor/SKILL.md, ../ln-627-diagnosability-auditor/SKILL.md, ../ln-628-concurrency-correctness-auditor/SKILL.md, ../ln-629-runtime-lifecycle-config-auditor/SKILL.md

Version: 5.0.0 Last Updated: 2025-12-23

FAQ

What does the ln-620-codebase-auditor skill do?

Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.

How do I install ln-620-codebase-auditor?

Run npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-620-codebase-auditor in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ln-620-codebase-auditor/ (personal) or .claude/skills/ln-620-codebase-auditor/ (project).

Which AI agents can use ln-620-codebase-auditor?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is ln-620-codebase-auditor safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains ln-620-codebase-auditor?

It is published by levnikolaevich in levnikolaevich/claude-code-skills. It has 449 recorded installs.

More from levnikolaevich/claude-code-skills

View all →

ln-100-documents-pipeline

levnikolaevich/claude-code-skills

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Docs & Writing479 installs

ln-775-api-docs-generator

levnikolaevich/claude-code-skills

Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.

Backend & APIs432 installs

ln-624-code-quality-auditor

levnikolaevich/claude-code-skills

Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.

413 installs

ln-782-test-runner

levnikolaevich/claude-code-skills

Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.

Testing & QA412 installs

ln-634-test-coverage-auditor

levnikolaevich/claude-code-skills

Open the skill to read its SKILL.md instructions.

Testing & QA401 installs

ln-201-opportunity-discoverer

levnikolaevich/claude-code-skills

Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.

Marketing & SEO398 installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.