an agent · maintained by you
Tend
A dutiful junior maintainer for your repo — quietly reviewing PRs, triaging issues, and looking after the corners no one else has time for.
claude plugin marketplace add max-sixty/tend
claude plugin install install-tend@tend
claude /install-tenda small field guide
A few of the things tend does, day to day.
PR reviews
Reads each pull request as it opens or updates. Traces error paths, names duplication, and flags places the change doesn't quite line up with what's already in the tree.
For PRs the bot itself authored, it goes further: it pushes the small mechanical fixes back to the branch so the human reviewer doesn't have to.
Issue triage
When an issue opens, tend classifies it, checks against the existing backlog for duplicates, and attempts to reproduce any reported bug.
If the fix is small and conservative, it'll draft one. Otherwise it leaves a clean, specific note for whoever picks the issue up.
Work delegation
Mention the bot in a PR or issue thread and it'll take a pass at what you asked — read the diff, run a check, draft a change, answer the question.
The human stays in the loop. Tend does the grunt work.
Nightly & weekly maintenance
Overnight it resolves merge conflicts on open PRs, reviews recent commits, sweeps a handful of files for stale docs and small bugs, and closes issues that have quietly been resolved.
On a weekly cadence it works through dependency PRs, auto-merging the safe patch and minor bumps it can verify.
Docs & code-quality audits
Each day tend reads the previous day's CI runs of its own workflows, looks for behaviour that didn't sit right, and proposes adjustments to its skills and config.
An agent that watches its own work, and edits its own instructions when it should.
getting started
Three commands and ten to fifteen minutes.
claude plugin marketplace add max-sixty/tend
claude plugin install install-tend@tend
claude /install-tend
The /install-tend skill walks the rest of the way:
config file, workflow generation, bot account, secrets, branch
protection. It'll ask before each step that touches your repo.
You'll need a GitHub account for the bot (something like
@your-project-bot) and a Claude Max subscription.
Maintainers of sizeable OSS projects can
get a Max subscription free from Anthropic
.
a question every adopter asks
Where the bot can and can't go.
Tend gives Claude write access to a repository. The primary boundary is a GitHub ruleset that prevents the bot from merging to protected branches — bot-authored PRs require human approval, and tend's setup script verifies and (if you ask) creates that ruleset for you. On top of that sit config-pinning, burst-and-spike rate limiting, and fixed workflow prompts that never read attacker-controlled input.