8/10

Strong

Claude Code is the closest match for a repo you will keep editing. Stated strengths are hooks, skills, project memory, and long multi-file work. Cost is a Claude subscription or API. Install is the official Claude Code setup, so day one starts in the docs, not with a command this page can honestly print. That gap keeps a Strong repo fit at 8, not Exceptional.

Cost: Claude subscription or API
Where it runs: Not stated
Standout trait: Hooks, skills, project memory, long multi-file work
Project file: CLAUDE.md

Install
curl -fsSL https://claude.ai/install.sh | bash
Open a repocd /path/to/your/repo
Give one taskRun claude. Ask for one reversible edit in a single file. Do not commit, and do not add flags.
Review the diffgit status then git diff. Keep or discard the edit yourself.

KeepTeach hooks, skills, and project memory as the reason to accept a docs-first install.

Best practices

Run 3–5 git worktrees at once, each with its own session. The Claude Code team calls that the biggest productivity gain. @bcherny 2026-01-31
Start every complex task in plan mode. If the work goes sideways, stop and re-plan. @bcherny 2026-01-31
After each correction, ask it to update CLAUDE.md so the same mistake does not repeat. Keep that file short. @bcherny 2026-01-31
If you do something more than once a day, turn it into a skill or slash command and commit it. @bcherny 2026-01-31
For a bug, paste the thread or the failing CI and say “fix”. Do not prescribe the steps. @bcherny 2026-01-31
Write the tests, commit them, and let it implement until they pass. @alexalbert__ 2025-04-21
Have one session write the code and a second session review it. @alexalbert__ 2025-04-21
Start subagents from /agents, then make the description precise so it picks the right one. @claude_code 2025-07-25