From 02965e41720aeee07ea56dbb133d95f0cce0f40c Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Sun, 9 Aug 2026 08:12:59 +0000 Subject: [PATCH 1/2] skills(running-in-ci): open the PR instead of filing an issue triage will convert --- plugins/tend-ci-runner/skills/running-in-ci/SKILL.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md b/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md index 68beb9a8..13efacec 100644 --- a/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md +++ b/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md @@ -88,6 +88,14 @@ Corollary: don't background anything whose output gates the deliverable. If a fu A pushed fix isn't done until its required checks are terminal — see **CI Monitoring**. +## Filing Issues in This Repo + +An issue here is not a note to a maintainer — `tend-triage` fires on `issues` and does the work. Filing one for a fix you have already scoped hands your own analysis to a second agent run, which re-derives it from your issue body and opens the PR minutes later at full session cost, on a thread nobody needed. + +So if you can open the PR in this run, open the PR. Reserve an issue for what you genuinely can't finish here: a problem too large or ambiguous to fix, one that needs a maintainer decision, or one whose verification is out of reach from CI. + +This governs your own repo only; filing into another repo follows the section below. + ## Filing Issues in Other Repos Default: file an issue in the current repo asking for permission to file in the target. On maintainer approval, file in the target. From d2cf4607f9930aab04ab082548ba1bc1428521d1 Mon Sep 17 00:00:00 2001 From: tend-agent <270458913+tend-agent@users.noreply.github.com> Date: Sun, 9 Aug 2026 08:20:41 +0000 Subject: [PATCH 2/2] skills(running-in-ci): condition on triage being enabled, carve out bookkeeping labels --- plugins/tend-ci-runner/skills/running-in-ci/SKILL.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md b/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md index 13efacec..29e05fe3 100644 --- a/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md +++ b/plugins/tend-ci-runner/skills/running-in-ci/SKILL.md @@ -90,9 +90,9 @@ A pushed fix isn't done until its required checks are terminal — see **CI Moni ## Filing Issues in This Repo -An issue here is not a note to a maintainer — `tend-triage` fires on `issues` and does the work. Filing one for a fix you have already scoped hands your own analysis to a second agent run, which re-derives it from your issue body and opens the PR minutes later at full session cost, on a thread nobody needed. +An issue here is not a note to a maintainer — where `tend-triage` is enabled (the default), it fires on `issues` and does the work. Filing one for a fix you have already scoped hands your own analysis to a second agent run, which re-derives it from your issue body and opens the PR minutes later at full session cost, on a thread nobody needed. -So if you can open the PR in this run, open the PR. Reserve an issue for what you genuinely can't finish here: a problem too large or ambiguous to fix, one that needs a maintainer decision, or one whose verification is out of reach from CI. +So if you can open the PR in this run, open the PR. Reserve an issue for what you genuinely can't finish here: a problem too large or ambiguous to fix, one that needs a maintainer decision, or one whose verification is out of reach from CI. Bookkeeping issues are a separate case, not this trade-off: `ci-fix`'s transient-diagnosis tracker carries `tend-outage`, which the generated `tend-triage` and `tend-mention` `if:` skip, so no conversion run fires. This governs your own repo only; filing into another repo follows the section below.