From 490a68ad8e11ee2f473b522ccdff8b7146d77e1d Mon Sep 17 00:00:00 2001 From: Lauri Gates Date: Tue, 6 Oct 2026 12:52:02 +0300 Subject: [PATCH] docs(claude): route code-triggered follow-ups to a tripwire test The Git Workflow rule sent every post-merge follow-up to a GitHub issue. A follow-up that waits on a condition in the source now goes in the same PR as a tripwire test, matching testing-plugin:test-tripwire and the session-wrap, git-issue and git-triage routing in laurigates/claude-plugins#2911. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01CpsxEu51MKyvB5otaHs1mr --- exact_dot_claude/CLAUDE.md | 1 + 1 file changed, 1 insertion(+) diff --git a/exact_dot_claude/CLAUDE.md b/exact_dot_claude/CLAUDE.md index 0b74cad1..f2d2b999 100644 --- a/exact_dot_claude/CLAUDE.md +++ b/exact_dot_claude/CLAUDE.md @@ -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