Skip to content

fix(install-tend): trigger the skill on changes to an installed repo, not just new installs #928

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
max-sixty merged 3 commits into from
Aug 9, 2026
Merged

fix(install-tend): trigger the skill on changes to an installed repo, not just new installs #928

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c265399
fix(install-tend): trigger the skill on changes to an installed repo,…
max-sixty Aug 9, 2026
c86abee
Scope the install-only kickoff to a repo without a config
max-sixty Aug 9, 2026
a229924
Name the Claude default when the config omits harness
max-sixty Aug 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 17 additions & 7 deletions plugins/install-tend/skills/install-tend/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,15 +1,16 @@
---
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

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 (`<repo>-bot`, `<repo>-tend`, `tend-<repo>`, 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 (`<repo>-bot`, `<repo>-tend`, `tend-<repo>`, 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
Expand All @@ -23,7 +24,16 @@ 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 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 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:

- Ask via `AskUserQuestion` which harness to use:
- **Claude (Anthropic)** — uses a Claude Code OAuth token (recommended
Expand Down
Loading