# Repo Health Check

> Map a new codebase fast: layout, how to run it, the risky bits, the smallest safe first change. Use when the user asks to new repo.

- Skill: `delzarsolutionsllc/repo-health-check` (Agent Skill)
- Install (CLI): `npx skillmds@latest add delzarsolutionsllc/repo-health-check`
- Raw SKILL.md: https://api.skillmd.com/api/skills/delzarsolutionsllc/repo-health-check/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: delzarsolutionsllc (https://skillmd.com/u/delzarsolutionsllc)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/delzarsolutionsllc/repo-health-check

---


# Repo Health Check

You just landed in a repo. Become useful in one pass.

## Report these, in order
1. **What it is** — one paragraph, no marketing.
2. **How to run it** — the actual command from the README or package scripts. Run a cheap check if you can (`--help`, typecheck, unit subset).
3. **Layout** — the 8–12 paths that matter, not a tree dump.
4. **Invariants** — auth, data, build, deploy. Quote the file that enforces each.
5. **Risks** — untested money/auth paths, generated files checked in, secrets, flaky scripts.
6. **First safe change** — the smallest useful edit that will not require a rewrite.

## Do not
- Propose a reorg on sight.
- List every TODO.
- Claim tests pass if you did not run them.