From 1fa90ce2f05f1039d36564032d816d91f46d53e6 Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Mon, 10 Aug 2026 07:22:42 +0000 Subject: [PATCH 1/2] fix(review): make the code-review second pass unconditional --- plugins/tend-ci-runner/skills/review/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/tend-ci-runner/skills/review/SKILL.md b/plugins/tend-ci-runner/skills/review/SKILL.md index 6375bb16..d39a742d 100644 --- a/plugins/tend-ci-runner/skills/review/SKILL.md +++ b/plugins/tend-ci-runner/skills/review/SKILL.md @@ -144,7 +144,7 @@ Scale depth to the change. A docs-only PR or a mechanical rename needs a skim fo Check the project's CLAUDE.md for language-specific review criteria and conventions. Load any project-specific review skill if available. -Review the diff two ways at once: the manual checks below, plus a `/tend-ci-runner:code-review` pass over the PR's merged tree. That skill is a structured second pass — correctness and cleanup angles, then a verify pass — and it returns findings rather than posting anything. Scale its depth to how core the change is, the same way you scale the manual depth above: +Review the diff two ways at once: the manual checks below, plus a `/tend-ci-runner:code-review` pass over the PR's merged tree. That skill is a structured second pass — correctness and cleanup angles, then a verify pass — and it returns findings rather than posting anything. **Every review that reaches this step runs it**, trivial diffs included — the depth-scaling above sets how deep the pass goes, never whether it happens. Scale its depth to how core the change is: - Peripheral or mechanical (docs, config, dependency bumps, test-only): tell it the change is peripheral, so it runs the short angle set in one pass. - The project's core logic: tell it the change is core, so it fans the angles out and sweeps for gaps. From 88472fb2db248483f77872b4394432a3f5b48f58 Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Mon, 10 Aug 2026 07:29:58 +0000 Subject: [PATCH 2/2] Lead with the mandate instead of the description --- plugins/tend-ci-runner/skills/review/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/tend-ci-runner/skills/review/SKILL.md b/plugins/tend-ci-runner/skills/review/SKILL.md index d39a742d..83eb16d2 100644 --- a/plugins/tend-ci-runner/skills/review/SKILL.md +++ b/plugins/tend-ci-runner/skills/review/SKILL.md @@ -144,7 +144,7 @@ Scale depth to the change. A docs-only PR or a mechanical rename needs a skim fo Check the project's CLAUDE.md for language-specific review criteria and conventions. Load any project-specific review skill if available. -Review the diff two ways at once: the manual checks below, plus a `/tend-ci-runner:code-review` pass over the PR's merged tree. That skill is a structured second pass — correctness and cleanup angles, then a verify pass — and it returns findings rather than posting anything. **Every review that reaches this step runs it**, trivial diffs included — the depth-scaling above sets how deep the pass goes, never whether it happens. Scale its depth to how core the change is: +**Every review that reaches this step runs a `/tend-ci-runner:code-review` pass over the PR's merged tree** — trivial diffs included; the depth-scaling above sets how deep the pass goes, never whether it happens. It's a structured second pass — correctness and cleanup angles, then a verify pass — that returns findings rather than posting anything, and it runs alongside the manual checks below rather than replacing them. Scale its depth to how core the change is: - Peripheral or mechanical (docs, config, dependency bumps, test-only): tell it the change is peripheral, so it runs the short angle set in one pass. - The project's core logic: tell it the change is core, so it fans the angles out and sweeps for gaps.