Vycari

Maintainerd — Data skill for Claude Code

Data community

Config-driven maintainer skills for Claude Code — a plugin marketplace of audits, daily ops, doc validation, and an autonomous issue→PR pipeline that drop into any repo via a small config contract.

How to install Maintainerd

This entry records only its repository, not the path inside it, so there is no exact command to give. Open Vycari/maintainerd and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Maintainerd does

Alternatives in Data

Data Contract — This document defines which files belong to the system (auto-updatable) and which belong to the user (never to 32.5k ★
Privacy & Data Handling — This repository contains: - a plugin package (plugins/compound-engineering) made of markdown/config content 10.8k ★
Query Token Info — Search tokens and fetch metadata, real-time market data, and K-Line candlestick charts by keyword or contract 483 ★

README

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`	Always — `bootstrap` generates the config every other plugin needs; `doctor` validates it.
repo-ops	`create-pr`, `address-review`, `release`, `daily-changelog`, `daily-update`	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.