Your repository buddy
repobuddy helps you to manage your repository.
Agent Skills
repobuddy provides agent skills for AI coding assistants (Claude Code, Cursor, etc.) to help manage your repository. Skills live in packages/buddy/skills/, ship inside the repobuddy npm package as a universal plugin, and install from a plugin marketplace or with the Skills CLI.
Available Skills
| Skill | Description |
|---|
agent-readiness | Score how ready a repo is for coding agents — a gated level, the three fixes worth the most, and the tokens every session loads — hold a level in CI, then fix the findings one area per commit, and benchmark what agents cost before and after; --package scores how easily consumers' agents can use a library |
epic | Plan an epic and its child issues — outcome first, unknowns as spikes — promote an issue to an epic, or demote an initiative, moving the work to the tracker that holds epics when the routing says so |
initiative | Set an initiative's goal and one metric — measure, baseline, target — and file its epics as shells for epic to break down, or promote an epic by creating the initiative above it |
issue | File a bug, feature, or task on GitHub, or on the tracker a routing names — searches for duplicates first |
llms-txt | Publish an llms.txt generated from a project's real public surface, with a CI drift check |
init-buddy | Set up the machine for the repo's git host — detects the OS and existing MCP servers, then installs and logs in gh, glab, tea, fj, or az, and proposes a starting harness allow list |
merge-dep-prs | Merge pending dependency update PRs — gates each merge on whether CI reached what the change can break, diagnoses CI failures, never merges release PRs |
min-release-age | Lift the minimum-release-age gate for one package version, restore it when the version ages past the window, and schedule the cleanup in CI |
project-tracker | Record which tracker holds each level and category of work — bugs on GitHub, epics elsewhere — and check the routing still resolves, so issue files where the team decided |
review-api | Review a library's public API for consistency and completeness against its own conventions — drift, sibling-justified gaps, docs vs exports |
scaffold | Create a new repository or package from a recipe a plugin ships — lists the installed recipes, asks the recipe's inputs, runs the host's setup skill, and writes nothing before you confirm the plan |
review-permissions | Audit what your agents are allowed to do — risk-rank every grant, then tighten and consolidate it |
checkpoint | create checkpoints from any agent session that a fresh session can continue from — next step first, settled decisions, open questions, in another repo when the work belongs there — and resume one without reopening settled decisions |
setup-github-repo | Set up a GitHub repo with branch protection, a merge backstop, Dependabot, and CI |
website | Work on a repo's docs website — init adds an Astro/Starlight site to a monorepo; deploy publishes a static site to GitHub, GitLab, or Codeberg Pages, Bitbucket, or Azure Static Web Apps |
to-question | Word a question for Slack, Jira, Linear, Asana, GitHub, GitLab, Bugzilla, Redmine, Trac, or email — checks the markup before you paste |
Installing as a Plugin
This repository is also a plugin marketplace. Claude Code and Codex read
.claude-plugin/marketplace.json, which installs the plugin from the repobuddy npm package, so the
built skill scripts come with it. Copilot CLI reads .github/plugin/marketplace.json, which installs
the plugin from this repository; its skills fall back to npx for their scripts. Copilot's docs also
list .claude-plugin/ as an alternate marketplace location it can read — deliberately kept out of sync
here, since its npm source shape isn't one of Copilot's documented source kinds (a relative path or a
git repository) and Copilot would fail to parse it.
Claude Code
/plugin marketplace add repobuddy/repobuddy
/plugin install repobuddy@repobuddy
Codex
codex plugin marketplace add repobuddy/repobuddy
codex plugin add repobuddy@repobuddy
GitHub Copilot CLI
copilot plugin marketplace add repobuddy/repobuddy
copilot plugin install repobuddy@repobuddy
Start a new session before using the plugin.
Cursor has no command-line install; a workspace admin imports the catalog from
Dashboard → Plugins → Team Marketplaces → Add Marketplace → Import from Repo.
See Install the skills for the update and uninstall
commands of each route.
Installing with the Skills CLI
For an agent without a plugin system:
List available skills:
npx skills add repobuddy/repobuddy --list
Install all skills:
npx skills add repobuddy/repobuddy
Install specific skills:
npx skills add repobuddy/repobuddy --skill issue --skill setup-github-repo
Some skills run scripts that are built at release and ship only in the npm package. Installed from
git as above, they run those scripts through npx -y repobuddy@<version> instead, which needs network
access. See Scripts and npx.
Update with npx skills update; uninstall with npx skills remove <skill> or npx skills remove --all.
Via Claude Code — ask Claude to find and install a skill:
find a skill for creating issues
or install directly:
/find-skills repobuddy/repobuddy
Related Skill Collections
These companion repositories provide additional skills often used alongside repobuddy:
Install from a related repo the same way:
npx skills add repobuddy/agent-changesets
Contains predefined configs for biome.
Contains various presets and config to customize jest.
Shared test utilities used across the repobuddy packages.
Provides tools and utilities to take care of TypeScript stuffs, so you don't have to.
Contains various presets and config to customize vitest.
CLI for managing your repository.
