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.
Plugin auto-dev from marketplace maintainerd in Vycari/maintainerd. Commands read from the repo's manifest — 2 days ago.
auto-devExecute one tick of the autonomous issue-to-PR pipeline — triage open issues for readiness, draft plans for maintainer approval, build the oldest approved issue into a PR, address review feedback; never merges; state lives in configurable auto:* GitHub labels. Designed to run as a recurring schedule
create-issueTurn a rough request into a well-formed GitHub issue that's ready for the auto-dev pipeline. Takes the user's description, then either investigates the codebase to isolate the affected files, likely root cause, and repro — or asks targeted clarifying questions when the ask is underspecified — and dr
review-queueThe maintainer's daily console for the auto-dev pipeline — gather everything blocked on you, present a worklist, loop executing your decisions against the `auto:*` state machine as you (never with the bot marker), until the queue drains. In an umbrella repo whose config carries a `workspace` block,
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.
6 skills
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.
5 skills · hooks
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.
3 skills
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.
1 skill
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.
1 skill
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.
1 skill
Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives
1 command
Tenant-isolated AI teams that plan work, coordinate tasks, recall approved context, and return evidence-backed results
6 skills · 6 commands · 4 agents · 1 MCP server
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
8 skills · 1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Install the "AAS Automation Builder" editorial skill bundle for Claude Code.
20 skills
Production incident management, triage workflows, and automated incident resolution
4 skills · 2 commands · 6 agents
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.