Baseline maintainer dev flow: create-pr (pre-flight-gated PRs), address-review (iterate on bot + human PR feedback to approval), release (cut a versioned release), daily-changelog, and the daily-update meta-skill. Plus two PreToolUse Bash hooks: pr-template-guard and skip-label-race-guard. Config-driven via .claude/maintainerd.json.
3 on GitHubby Allen Hutchisonv0.8.8MITupdated 2 days ago
/
Plugin repo-ops from marketplace maintainerd in Vycari/maintainerd. Commands read from the repo's manifest — 2 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
What it installs
Skills (5)
address-review
Drive the iterative response loop on a PR you own — fetch every piece of review feedback (automated reviewers like CodeRabbit / gemini-code-assist AND human reviewers), triage it, fix the real issues with one focused commit each, run the repo's pre-flight, push, then post a reply to every thread (in
create-pr
Create a pull request for the current repository the right way — enforce the repo's PR template, run a `/simplify` pass and a `code-review` self-review, then every CI gate (format, lint, build, typecheck, tests) locally before pushing, require docs updates for user-facing changes, and write an hones
daily-changelog
Generate a daily changelog / release-notes document from the PRs that merged on a given date and write it to `config.paths.changelogDir` as `YYYY-MM-DD.md`. Use when the user asks for "the daily changelog", "daily release notes", "release notes", "what shipped today/yesterday", "what landed on <date
daily-update
Run the repo's per-day housekeeping skills and bundle their output into one PR. Each sub-skill writes to the working tree (or mutates GitHub directly); this skill runs the configured roster in sequence, collects what they wrote, and packages the combined diff into a single PR. Use when the user asks
release
Cut a versioned release of the repo — gather every change since the last tag (not just this session), update the repo's release notes / changelog, run the pre-flight checks and the repo's final release gate, bump the version via the repo's configured mechanism, push the tag, create/publish the GitHu
Scheduled findings that open PRs/issues, deliberately capped and conservative: audit-architecture, audit-tests, audit-security, audit-deps, audit-design-docs, audit-product-docs. Language and rules come from the repo config + guidelines files.
Autonomous issue-to-PR pipeline driven by an auto:* GitHub label state machine: create-issue (turn a rough request into a buildable issue), auto-dev (triage -> plan -> build -> address-review; never merges), and review-queue (the maintainer's console). Configurable label names, markers, and branch prefixes.
Foundation: bootstrap (generates a repo's .claude/maintainerd.json config contract), doctor (validates that setup, and reports drift from a fleet's repo standard with --profile) and new-repo (creates or adopts a repo against that standard), plus the canonical config schema every other plugin reads. Install this first.
Autonomous Dependabot queue management — the one maintainerd plugin that merges. dependabot gates each bot-authored dependency PR on all checks green, no requested changes, and a semver policy (patch/minor by default; majors held for you), merges one PR per non-overlapping file group, waits for the rebase, and repeats until the queue drains. A broken update is never fixed: it's diagnosed, filed as an issue, and labelled. Requires an explicit depsFlow.enabled opt-in.
User-scoped narration that spans repos: worklog captures a day's shipped work (merged PRs enriched by the live session) into the user's Obsidian vault. Vault path lives in a user-level ~/.claude/maintainerd.json; a per-repo pointer maps each repo to its vault project.
Proactive research skills that surface relevant outside knowledge and open a PR/digest: research-radar (periodic arXiv scan for papers relevant to this repo). Room for future research tooling. Themes and output paths come from the repo config.
Legacy core-only installation. For the release-managed bundle of every skill, install hyperframes@hyperframes and then uninstall core-skills@hyperframes.
Investigate incidents, review code and execute UAT for release readiness, scan code for vulnerabilities, and run penetration tests with AWS DevOps Agent and AWS Security Agent.
Audit and rewrite prose that reads as machine-generated, across READMEs, changelogs, PR descriptions, docs, and blog copy, with detect-only, rewrite, and edit-in-place modes.
Prepares a repository for public open-source release: secrets-history hygiene, license selection, documentation and CI readiness checks, and language-specific packaging and release guidance.
Write an Amazon-style press release that defines customer value before building.
1 skill
deanpeters/Product-Manager-Skills 8,001
Maintain repo-ops?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.