Vycari/maintainerd

Maintainerd is a Claude Code plugin marketplace of config-driven maintainer skills — the nightly
audits, daily changelog, doc validation, PR flow, and autonomous issue→PR pipeline that a
solo maintainer wants on every repo, extracted so they live in one place instead of being
copy-pasted (and drifting) across projects.
Every skill reads a small per-repo config contract — .claude/maintainerd.json plus a few
.claude/guidelines/.md files — checked into the consuming repo. The same skill runs
unchanged in a Python repo and a TypeScript repo; only the config differs. The bootstrap
skill generates that contract for any repo.
## Plugins
| Plugin | Skills | Install when |
| maintainerd-core | bootstrap, doctor, new-repo | Always — bootstrap generates the config every other plugin needs; doctor validates it; new-repo brings a repo to a fleet's standard. |
| repo-ops | create-pr, address-review, release, daily-changelog, daily-update (plus three PreToolUse Bash hooks, pr-template-guard, skip-label-race-guard and merge-guard, and an opt-in PostToolUse hook, review-reply-postcondition) | You want the baseline PR + changelog dev flow. |
| audits | audit-architecture, audit-tests, audit-security, audit-deps, audit-design-docs, audit-product-docs | You want scheduled tech-debt / test / security / dependency / doc sweeps. |
| research | research-radar | You want proactive research surfaced — a periodic arXiv scan for papers relevant to this repo. |
| journal | worklog | You want a day's shipped work captured into your Obsidian vault (user-scoped — spans all your repos). |
| auto-dev | create-issue, auto-dev, review-queue | You want the autonomous issue→PR pipeline (from issue intake through build to review). |
| deps-flow | dependabot | You want the Dependabot queue drained unattended — and you're willing to let a skill merge. |
A repo installs only the plugins it wants. auto-dev works standalone (with maintainerd-core
for config); the audits and repo-ops compose but don't require each other.
> deps-flow is the exception to the suite's "never auto-merges" rule. Every other skill stops
> at the merge gate; dependabot merges dependency PRs that pass a strict gate (all checks
> concluded green, no requested changes, bump level within the repo's policy). It requires an
> explicit depsFlow.enabled: true — an absent config block means off, never defaults. Run
> /dependabot dry-run first.
## Setup in a new repo
1. Add the marketplace (once per machine):
bash
claude plugin marketplace add Vycari/maintainerd
# or, for local development:
claude plugin marketplace add /path/to/your/checkout/maintainerd
2. Install the plugins you want, starting with core:
text
/plugin # then install maintainerd-core, repo-ops, audits, research, auto-dev as desired
3. Generate the config by running the bootstrap skill in the target repo:
text
/bootstrap
It inspects the repo (language, repo slug, default branch, source/test dirs, lint/test
commands), confirms anything ambiguous with you, and writes:
.claude/maintainerd.json — the structured config (see
plugins/core/references/config-schema.md).
.claude/guidelines/coding.md, testing.md, invariants.md — starter guideline files