What commands should every CLAUDE.md include?

At minimum: install, dev, lint, test, typecheck if separate, build, and deploy or release notes if the repo has them.

Should production deploy commands go in CLAUDE.md?

Yes, but label them clearly and include any approval, branch, or profile constraints so the agent does not run them casually.

Can the reviewer find missing commands automatically?

It can flag missing sections and likely gaps, but you should still compare the output with the actual repo scripts and CI config.

Agent instruction guide

CLAUDE.md Missing Commands Checklist

Check whether a CLAUDE.md includes the build, test, lint, dev server, deploy, and verification commands an agent needs before editing.

Direct answer

A useful CLAUDE.md should list the commands an agent needs to work safely: install, dev server, lint, typecheck, test, build, deploy, formatting, and any special environment or profile commands. If those are missing, the agent has to guess, which leads to skipped verification and broken handoffs.

Open CLAUDE.md Reviewer

When to use this

A generated CLAUDE.md only describes the stack but not commands.
Agents keep asking how to run tests or builds.
The repo has special profiles, environment variables, or deploy paths.

Steps

List the real commands from package scripts, Makefiles, CI, or docs.
Add the normal verification command sequence.
Call out commands that require special profiles or credentials.
Label commands that are expensive, destructive, or deploy production.
Run the reviewer to catch missing or vague command sections.

Example review focus

CLAUDE.md excerpt

# CLAUDE.md

This repo is a React app. Use TypeScript and do not break anything.

## Style
Follow existing patterns.

What to fix

Add a Commands section: dev server, lint, test, build, deploy trigger, and any required environment variables. Replace `do not break anything` with a concrete verification gate such as `npm run lint && npm run test && npm run build` before final when relevant.

Common mistakes

Do not invent commands that are not in the repo.
Do not hide deploy commands inside prose.
Do not omit environment profiles, SSO, or credentials that affect verification.

FAQ

What commands should every CLAUDE.md include?: At minimum: install, dev, lint, test, typecheck if separate, build, and deploy or release notes if the repo has them.
Should production deploy commands go in CLAUDE.md?: Yes, but label them clearly and include any approval, branch, or profile constraints so the agent does not run them casually.
Can the reviewer find missing commands automatically?: It can flag missing sections and likely gaps, but you should still compare the output with the actual repo scripts and CI config.

Related CLAUDE.md guides

Review CLAUDE.md for Token Waste

Find vague, repeated, or unused CLAUDE.md instructions that cost tokens every Claude Code turn without improving behavior.

CLAUDE.md Repo Boundaries and Rules

Write CLAUDE.md rules that tell agents which files to edit, which files to avoid, and how to handle dirty worktrees safely.

Review CLAUDE.md Before Converting to AGENTS.md

Clean a CLAUDE.md first, then convert it into AGENTS.md, Cursor rules, GitHub Copilot instructions, or Windsurf rules.

What Should Go in a CLAUDE.md File

Decide what belongs in CLAUDE.md and what belongs in the README, a path-scoped rule, or a skill. One test per line, applied to a real file.

Claude Code Is Not Following CLAUDE.md — How to Fix It

Diagnose why Claude Code ignores your CLAUDE.md: the file never loaded, the rule is vague, two files contradict, or the rule needs a hook instead.

CLAUDE.md vs .claude/rules vs Skills — Which File Owns What

Route each instruction to the right file: always-loaded CLAUDE.md, path-scoped .claude/rules/, or on-demand skills. One question decides it.

CLAUDE.md Best Practices Checklist — Audit Your File Against 8 Rules

Run your CLAUDE.md through eight checks: size, specificity, exact commands, anti-patterns, structure, contradictions, enforcement, and staleness.

Desk gear for long writing sessions

A few things that help if you write docs, tickets, and specs on a laptop all day.

Dock

Anker 5-in-1 USB-C Hub

One cable turns a laptop into a desk setup. Drives a 4K display, charges at up to 85W, and adds three data ports.

4K HDMI output
85W max power delivery
1x USB-C + 2x USB-A, 5Gbps each
MacBook Pro, MacBook Air, Dell

Check price on Amazon →Monitor · I use this

Dell 27" S2725QC 4K

The monitor I write and review documents on. 163 PPI keeps small text sharp, and USB-C carries video and power on one cable.

3840x2160 IPS, 163 PPI
120Hz, 4ms, FreeSync Premium
99% sRGB
USB-C, HDMI, DisplayPort

Check price on Amazon →Laptop

Apple MacBook Neo 13" (A18 Pro)

The cheapest way into an Apple-silicon machine that runs local models. Fanless, and the Liquid Retina panel holds small text at a full day of reading.

A18 Pro chip, built for Apple Intelligence
8GB unified memory, 256GB SSD
13-inch Liquid Retina display
1080p FaceTime HD camera

Check price on Amazon →

Amazon affiliate links. We earn a commission on qualifying purchases at no extra cost to you.