Skip to content

docs(claude): route code-triggered follow-ups to a tripwire test #470

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
laurigates merged 1 commit into from
Oct 6, 2026
Merged

docs(claude): route code-triggered follow-ups to a tripwire test #470

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions exact_dot_claude/CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ Personal configuration for Claude Code. Domain-specific skills and workflows are
## Git Workflow

- When creating PRs that require post-merge follow-up actions (e.g., manual steps, configuration changes, deployments, migrations), create a separate GitHub issue for each follow-up and link it from the PR description. Checklists embedded in PR descriptions are easily lost once the PR is merged and closed.
- Exception: a follow-up that waits on a condition visible in the source (a list outgrowing a limit, an enum gaining a member, a version bump) goes in the same PR as a tripwire test that fails when the condition comes true, not as an issue — see `testing-plugin:test-tripwire`.

## Debugging

Expand Down
Loading