claude/skills/worktree-testing/SKILL.md
Guide for testing changes locally when working in a Claude Code worktree. Use when running dev servers, tests, or verifying changes in a worktree.
npx skillsauth add iainmcl/dotfiles worktree-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Worktrees (claude -w <name>) create an isolated copy of the repo at
.claude/worktrees/<name>/ on a new branch worktree-<name>.
Dependencies are not pre-installed in a new worktree. Install them before running anything:
# Frontend
cd frontend && npm install
# Backend
cd backend && pip install -e ".[dev]"
Run just run or individual dev commands as normal — the worktree is a full
working copy.
Port conflicts: If the main repo is already running dev servers, the worktree will fail to bind the same ports. Stop the main instance first or configure different ports.
Open another terminal and cd into the worktree directory to run servers,
curl endpoints, or open the browser while Claude works in the session:
cd .claude/worktrees/<name>/
just run
When exiting the Claude session:
development
Run a weekly achievement review - pulls from Jira, GitHub, and Slack to capture what you shipped in the last week, maps achievements to your 2026 goals, and appends impact-focused entries to your brag doc. Use when asked to "do a weekly review", "capture this week's wins", "update my brag doc", "what did I ship this week", "record my achievements", "what have I done this week", "add to my performance doc", or anything about tracking weekly progress, brag doc entries, or performance evidence. Trigger even if the user just says "weekly review" or "document what I did".
testing
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
tools
Set up a project update config for the current repo, so that running project-update requires no setup questions. Use when asked to "set up project updates", "configure project update", "initialise project update", or "create a project update config". Run this once per project repo.
testing
Find the highest-frequency unresolved Sentry error for the VAT & Invoicing or Billing team, understand its root cause, create a Jira ticket in the APP project, implement a fix, and open a draft PR. Use when asked to "fix sentry issues", "triage sentry errors", "look at sentry", "what's broken in sentry", "create a fix for a sentry issue", or "sentry triage". Runs the full flow autonomously in the background.