From c2653998adf51e9d39626dbcc115fa8fef8d9a2a Mon Sep 17 00:00:00 2001 From: Maximilian Roos Date: Sun, 9 Aug 2026 05:01:57 -0700 Subject: [PATCH 1/3] fix(install-tend): trigger the skill on changes to an installed repo, not just new installs Co-Authored-By: Claude Opus 5 (1M context) --- plugins/install-tend/skills/install-tend/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/install-tend/skills/install-tend/SKILL.md b/plugins/install-tend/skills/install-tend/SKILL.md index f4d3ae77..1a765dcc 100644 --- a/plugins/install-tend/skills/install-tend/SKILL.md +++ b/plugins/install-tend/skills/install-tend/SKILL.md @@ -1,6 +1,6 @@ --- name: install-tend -description: Sets up tend — an autonomous junior maintainer for a GitHub repo, powered by Claude or OpenAI Codex — that reviews PRs, triages issues, and fixes CI. Creates config, generates workflows, configures secrets and branch protection via API, creates the bot account, and provisions the harness auth token (Claude OAuth or OpenAI API key). Use when setting up tend on a new repo or when asked to install/configure tend. +description: Sets up tend — an autonomous junior maintainer for a GitHub repo, powered by Claude or OpenAI Codex — that reviews PRs, triages issues, and fixes CI. Creates config, generates workflows, configures secrets and branch protection via API, creates the bot account, and provisions the harness auth token (Claude OAuth or OpenAI API key). Use when installing tend, when clearing a failing `tend check`, and when changing an installed repo's tend config, generated workflows, secrets, environments, branch protection, or bot access. --- # Install Tend From c86abee6f90a28511466798c18c40533bdd40b1c Mon Sep 17 00:00:00 2001 From: Maximilian Roos Date: Sun, 9 Aug 2026 05:14:00 -0700 Subject: [PATCH 2/3] Scope the install-only kickoff to a repo without a config Co-Authored-By: Claude Opus 5 (1M context) --- .../install-tend/skills/install-tend/SKILL.md | 20 +++++++++++++------ 1 file changed, 14 insertions(+), 6 deletions(-) diff --git a/plugins/install-tend/skills/install-tend/SKILL.md b/plugins/install-tend/skills/install-tend/SKILL.md index 1a765dcc..ad9e286d 100644 --- a/plugins/install-tend/skills/install-tend/SKILL.md +++ b/plugins/install-tend/skills/install-tend/SKILL.md @@ -5,11 +5,12 @@ description: Sets up tend — an autonomous junior maintainer for a GitHub repo, # Install Tend -Set up tend on the current repo. If the user hasn't supplied a bot name, -get one via `AskUserQuestion` before step 1 using the candidate-generation -pattern from step 6 (`-bot`, `-tend`, `tend-`, parallel -availability check, present available ones). The user can pick "Other" -to supply a custom name. +Set up tend on the current repo, or change an installation it already has. +When installing and the user hasn't supplied a bot name, get one via +`AskUserQuestion` before step 1 using the candidate-generation pattern from +step 6 (`-bot`, `-tend`, `tend-`, parallel availability +check, present available ones). The user can pick "Other" to supply a custom +name. When asking the user questions during these steps, use the `AskUserQuestion` tool — present concrete options when there are clear choices (e.g. bio @@ -23,7 +24,14 @@ not have to ask "where do I do that?". ## Kickoff -Before running step 1, choose the harness and lay out the plan: +Read `.config/tend.yaml` first. Its presence says whether this is an install or +a change to one, and where it exists it already names the harness. + +With a config in place, take `harness` from it, lay out only the steps the task +touches, and start. The summary checklist at the end describes a finished +install, so skip it. + +With no config yet, choose the harness and lay out the whole install: - Ask via `AskUserQuestion` which harness to use: - **Claude (Anthropic)** — uses a Claude Code OAuth token (recommended From a2299243b2960ac0af1fe8241fb598e4da4e5e28 Mon Sep 17 00:00:00 2001 From: Maximilian Roos Date: Sun, 9 Aug 2026 05:26:51 -0700 Subject: [PATCH 3/3] Name the Claude default when the config omits harness Co-Authored-By: Claude Opus 5 (1M context) --- plugins/install-tend/skills/install-tend/SKILL.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/plugins/install-tend/skills/install-tend/SKILL.md b/plugins/install-tend/skills/install-tend/SKILL.md index ad9e286d..a325f4f4 100644 --- a/plugins/install-tend/skills/install-tend/SKILL.md +++ b/plugins/install-tend/skills/install-tend/SKILL.md @@ -25,10 +25,12 @@ not have to ask "where do I do that?". ## Kickoff Read `.config/tend.yaml` first. Its presence says whether this is an install or -a change to one, and where it exists it already names the harness. +a change to one, and where it exists it settles the harness: the `harness` key, +or Claude when the key is absent, which is how a Claude install is normally +written. -With a config in place, take `harness` from it, lay out only the steps the task -touches, and start. The summary checklist at the end describes a finished +With a config in place, take the harness from it, lay out only the steps the +task touches, and start. The summary checklist at the end describes a finished install, so skip it. With no config yet, choose the harness and lay out the whole install: