Install and shell
Confirm the claude command resolves in the shell you actually use, then document any local environment variables separately from shared repo files.
Free Tool
Free Claude Code Setup Checklist Generator
A Claude Code setup checklist generator creates a practical runbook for installing Claude Code, documenting repository context, setting permissions, adding MCP servers, validating Git workflow, and running the first verification commands.
Configure the checklist
Generated setup plan
- 1Install Claude Code with npm using the package and version recommended by Anthropic's current docs.
- 2Run claude --version to confirm the command is available.
- 3Keep Node.js on a current LTS release so CLI updates and hooks run reliably.
- 4Use ~/.zshrc for shell-specific environment setup, then add only keys or aliases that belong on this machine.
- 5Open ~/src/my-app and run git status before asking Claude Code to modify files.
- 6Create or update CLAUDE.md with repo commands, coding conventions, test expectations, deployment notes, and review preferences for this existing repository.
- 7Set permissions profile: Allow normal repo reads, edits, lint/test/build commands, and ask before installs, pushes, or destructive commands.
- 8Confirm the primary verification command works manually: npm run build.
- 9Add MCP servers only after the base CLI works. Start with one read-only server, verify it, then add higher-risk servers one at a time.
- 10Document each MCP server's purpose, auth source, and allowed scope in CLAUDE.md or project docs.
- 11Make a small test branch or commit so you can verify Claude Code respects the Git workflow before larger changes.
- 12Ask Claude Code to summarize git diff before committing and to leave unrelated worktree changes alone.
- 13Run one low-risk prompt that reads the repo and explains the app structure before requesting edits.
Starter commands
npm install -g @anthropic-ai/claude-code cd ~/src/my-app git status --short test -f CLAUDE.md || touch CLAUDE.md npm run build # Add MCP servers after base CLI verification, then test them one at a time. claude --print "Read this repo and summarize the main app structure, verification commands, and any setup risks. Do not edit files."
How to use the Claude Code setup checklist
- Choose the install state. Pick whether Claude Code still needs to be installed, was installed natively, or is already available on your machine.
- Set repository context. Enter the repository path, shell, project type, and primary verification command so the checklist matches the real setup.
- Pick permissions and integrations. Choose the permission posture and whether to include MCP, Git workflow, and team handoff steps.
- Copy the checklist. Copy or download the generated Markdown and use it as the setup runbook before asking Claude Code to edit files.
What belongs in a Claude Code setup checklist?
Repo memory
Use CLAUDE.md to record commands, conventions, test scope, deployment rules, and review expectations so each run starts with the same context.
Permissions
Start with explicit allow, ask, and deny rules so Claude Code can work quickly without surprising installs, pushes, secret reads, or destructive commands.
Claude Code setup FAQ
What is a Claude Code setup checklist generator?
A Claude Code setup checklist generator creates a tailored install and configuration checklist for Claude Code, including shell setup, CLAUDE.md, permissions, MCP servers, Git workflow, and first verification commands.
What should I do before asking Claude Code to edit files?
Confirm the CLI starts, open the repository, run git status, document repo commands in CLAUDE.md, and run one read-only prompt that explains the project before requesting edits.
Should team Claude Code settings be committed?
Commit shared guidance such as CLAUDE.md and safe .claude/settings.json rules, but keep personal paths, local secrets, and machine-specific overrides in .claude/settings.local.json.
When should I add MCP servers?
Add MCP servers after the base Claude Code workflow works. Start with one read-only server, verify it, then add higher-risk servers one at a time.
Does this checklist store my repository details?
No. The checklist generator runs in your browser and only creates copyable text from the options you choose.
Related Tornic tools
Build the companion config files after your base setup is ready.