sentry-fix

Topics in the source

• Sentry fix
• Terms
• 1. Find the project
• 2. Derive the Sentry setup
• 3. Choose the issues
• 4. Prepare
• 5. Fix in parallel
• 6. Clean up

Works in any repo whose Sentry DSNs are committed, from any folder. Everything is derived; nothing is configured per repo. Lookup: ${CLAUDESKILLDIR}/project.sh, run with VAULT and PROJECTSROOT set to the vault and projects root named in /.claude/CLAUDE.md. It prints key: value lines; project: none comes with a reason:. : the project's main checkout (the lookup's dir). Every git command runs as git -C … or git -C …, so the current folder never matters. : the issue's short id, lowercased (ACME-4F2 → acme-4f2). Worktree: /.claude/worktrees/sentry-fix- on branch sentry-fix/ . Code bug: the stack trace points into this repo's code and a change there stops the error. Infra, config, network, browser extensions, third-party outages and anything you can't pin down are not. Run the lookup in the current folder. project: none, or the caller named another project (e.g. /briefing hands over the project name) → run the lookup with --note . Still no dir → ask Quinn for the project folder once. With a note, write the answer into its frontmatter as local: , so the lookup finds it next time. Done when: is a git checkout, and the project note is known or confirmed absent. 1. Projects: ${CLAUDESKILLDI

This is an excerpt. Refer to the complete source and its current requirements.