tend
An agent that tends your repo — reviewing PRs, triaging issues, and responding to whatever comes up, so you can focus on building beautiful things.
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 where the change cuts against the existing code.
On its own PRs it goes further — pushes the small mechanical fixes straight to the branch.
Issue triage
When an issue opens, tend classifies it, checks the backlog for duplicates, and tries to reproduce any reported bug.
If the fix is small and conservative, it'll open a PR. Otherwise it leaves a clear note for whoever picks it up.
CI fixes
When the default branch goes red, tend reads the failed run, finds the underlying cause, and opens a PR with the fix.
Work delegation
Mention the bot in a PR or issue and it takes a pass at what you asked — resolve a merge conflict, draft a change, research a question, fix the tests.
Nightly & weekly maintenance
Overnight it sweeps a rotating sample of files for stale docs and small bugs, reviews the day's commits, resolves merge conflicts on its own open PRs, and closes issues that got fixed.
Each week it works through dependency PRs — approving the patch and minor bumps with green CI, flagging the rest.
Self-review
Each day tend reads the previous day's runs of its own workflows, looks for behaviour that didn't sit right, and proposes adjustments to its Skills and config.
how it works
A subscription, some workflows, and Skills you can shape.
Tend runs Claude Code in GitHub Actions, using your Claude Max subscription.
In your repo, Tend is a handful of GitHub Actions workflows, each running a Skill, generated from a single config.
Skills and docs in your repo overlay Tend's defaults. Set what it auto-approves, calibrate what it flags in reviews, have it close some category of PR on sight, or give it a new chore to run each night.
recent ground
A few of the last things the bots have touched.
getting started
Claude Code sets Tend up in about ten minutes.
claude plugin marketplace add max-sixty/tend
claude plugin install install-tend@tend
claude /install-tendThe /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.
security
Where the bot can and can't go.
Tend gives Claude write access to a repository. The primary boundary is a GitHub ruleset that blocks the bot from merging to protected branches — whoever opened the PR, however it's been reviewed — so every change lands through a human merge; 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 a fixed prompt and Skill set: an attacker who controls a PR diff or an issue body can shape what Claude reads, never the instructions it follows.