deps-flow
🔌Pluginallenhutchison/maintainerd
Installation
/plugin marketplace add allenhutchison/maintainerd/plugin install deps-flow@maintainerd
|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.
Part of
allenhutchison/maintainerd
More from this repository7
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. Config-driven via .claude/maintainerd.json.
Foundation: bootstrap (generates a repo's .claude/maintainerd.json config contract) and doctor (validates that setup and reports what's wrong), plus the canonical config schema every other plugin reads. Install this first.
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.
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.
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.
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.