Set up CLAUDE.local.md for a new contributor to the seminr-issues repo. Use when a maintainer needs to configure their local environment.
Set up CLAUDE.local.md so this repo can access the local seminr codebase.
Check if already configured: Read CLAUDE.local.md in the project root. If it exists and has content, show it to the user and ask if they want to reconfigure or keep it.
Locate the seminr repo: Check if a sibling seminr directory exists at ../seminr relative to this repo's root. Verify it's a git repo with test -d ../seminr/.git.
sem-in-r/seminr is. Recommend cloning it as a sibling directory:
cd <parent of seminr-issues>
git clone [email protected]:sem-in-r/seminr.git
Worktrees directory: Check if ../seminr-worktrees/ exists as a sibling.
mkdir ../seminr-worktrees
Write CLAUDE.local.md: Once paths are confirmed, write the file using this template (substitute actual absolute paths):
# CLAUDE local environment
## SEMinR Codebase
Local seminr source (for code investigation, git history, running tests):
`<SEMINR_PATH>`
Worktrees: `<WORKTREES_PATH>`
## Planning Documents
Main development queue: @triage.md
Other documents (read on demand, not auto-loaded):
- `next-release.md` — PRs merged to develop, issues to close on next release
- `releases/` — release history, closed issues, archived PRs
If the user opted out of worktrees, omit the Worktrees: line.