From 56f616d1c119944bf3377b0a17a09f5b1fca601f Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Thu, 6 Aug 2026 00:20:32 +0000 Subject: [PATCH 1/2] fix(review-reviewers): give each matrix leg its own PR branch name The workflow matrixes over five target repos and every leg shares one $GITHUB_RUN_ID, so the Step 5 recipe named the same branch for all of them. Two legs that both find something race one ref: one push is rejected, or worse, two unrelated concerns land on a single branch. Append the target repo name to the recipe. --- plugins/tend-ci-runner/skills/review-reviewers/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md b/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md index b9af0f82..0edbff6c 100644 --- a/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md +++ b/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md @@ -353,7 +353,7 @@ Search titles AND bodies for related keywords. Only comment on existing issues i **Prefer PRs over issues.** A PR with a clear description is immediately actionable. -- **PR** (default): Branch `hourly/review-$GITHUB_RUN_ID`, fix, commit, push, create with label `claude-behavior`. Put full analysis in PR description (run ID, outcome evidence, root cause, **gate assessment** including historical evidence count). Don't also create a separate issue. +- **PR** (default): Branch `hourly/review-$GITHUB_RUN_ID-`, fix, commit, push, create with label `claude-behavior`. The workflow matrixes over target repos and every leg carries the same `$GITHUB_RUN_ID`, so the run ID alone is not a unique branch name — append the target's repo name (the part after the `/`) to keep two legs that both find something from racing the same ref. Put full analysis in PR description (run ID, outcome evidence, root cause, **gate assessment** including historical evidence count). Don't also create a separate issue. - **Issue** (fallback): Only for problems too large or ambiguous to fix directly. Include run ID, outcome evidence, root cause analysis. Group multiple findings by broad theme. **Limit to at most 2 PRs per run** — if you have more findings, pick the highest-confidence ones and record the rest in the evidence gist. From c8628f6240ef398b5102ad4a91ee51784812d0ee Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Thu, 6 Aug 2026 00:27:23 +0000 Subject: [PATCH 2/2] review-reviewers: add a topic slug so one leg's two PRs don't collide either --- plugins/tend-ci-runner/skills/review-reviewers/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md b/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md index 0edbff6c..f137e2fd 100644 --- a/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md +++ b/plugins/tend-ci-runner/skills/review-reviewers/SKILL.md @@ -353,7 +353,7 @@ Search titles AND bodies for related keywords. Only comment on existing issues i **Prefer PRs over issues.** A PR with a clear description is immediately actionable. -- **PR** (default): Branch `hourly/review-$GITHUB_RUN_ID-`, fix, commit, push, create with label `claude-behavior`. The workflow matrixes over target repos and every leg carries the same `$GITHUB_RUN_ID`, so the run ID alone is not a unique branch name — append the target's repo name (the part after the `/`) to keep two legs that both find something from racing the same ref. Put full analysis in PR description (run ID, outcome evidence, root cause, **gate assessment** including historical evidence count). Don't also create a separate issue. +- **PR** (default): Branch `hourly/review-$GITHUB_RUN_ID--`, fix, commit, push, create with label `claude-behavior`. `$GITHUB_RUN_ID` alone is not a unique branch name: every matrix leg of a tick carries the same one, and a single leg may open two PRs (see the 2-PR limit below). The target's repo name (the part after the `/`) keeps two legs from racing the same ref; the topic slug keeps one leg's two PRs from doing the same. Put full analysis in PR description (run ID, outcome evidence, root cause, **gate assessment** including historical evidence count). Don't also create a separate issue. - **Issue** (fallback): Only for problems too large or ambiguous to fix directly. Include run ID, outcome evidence, root cause analysis. Group multiple findings by broad theme. **Limit to at most 2 PRs per run** — if you have more findings, pick the highest-confidence ones and record the rest in the evidence gist.