# Review Codebase Design

> Codebase design review for internal module boundaries, dependency direction, coupling, cohesion, domain modelling, layering, complexity, duplication, and observed patterns. Use for maintainability, modularity, or within-repository architecture questions.

- Skill: `kenlck/review-codebase-design` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add kenlck/review-codebase-design`
- Raw SKILL.md: https://api.skillmd.com/api/skills/kenlck/review-codebase-design/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: kenlck (https://skillmd.com/u/kenlck)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/kenlck/review-codebase-design

---


# Review codebase design

Assess one repository, a repository group, or an existing fleet evidence bundle. Describe the structure that exists and the change pressure it creates without assuming undocumented intent.

## Run the lens

1. Read the [standalone lens protocol](../audit-software-fleet/references/standalone-lens.md) completely and prepare the supplied scope with lens ID `codebase-design`.
2. Read [the codebase design checks](references/checks.md) completely. Apply every check family relevant to the repository shape, language, framework, and domain.
3. Trace representative dependency and change paths across modules. Classify supported outcomes as strengths or findings; label patterns and boundaries as observed or inferred and record missing context as unknowns.
4. Follow the protocol to account for every contract-registered check family, validate the result, ingest it, and hand back the canonical artifact path.

For raw collection or generated dependency analysis, read and follow the [safety model](../audit-software-fleet/references/safety-model.md). Keep the source repository unchanged.

## Boundary

Own internal repository structure and maintainability. Route cross-repository contracts and coupling to system integration, organizational controls to governance, and runtime performance claims to performance efficiency.

## Completion

**Complete when:** every in-scope repository has an exact commit or explicit unavailable state, every applicable check family is accounted for, every claim has bounded sanitized evidence at an appropriate confidence, gaps remain visible in unknowns and coverage, and the shared result validator succeeds.