---
title: "repo-ops"
description: "Baseline maintainer dev flow as config-driven skills: create-pr (opens PRs only after running the repo's format/lint/build/test pre-flight), address-review (drive the iterative response loop on bot + human PR feedback to"
canonical: https://agentpluginsdirectory.com/plugins/repo-ops
last-updated: 2026-10-08
---

# repo-ops
Baseline maintainer dev flow as config-driven skills: create-pr (opens PRs only after running the repo's format/lint/build/test pre-flight), address-review (drive the iterative response loop on bot + human PR feedback to approval, fix, push, reply to every inline thread and a PR-level summary), release (cut a versioned release: gather changes since the last tag, update notes, run the gate, bump, tag, publish), daily-changelog (one markdown file per day from merged PRs), and daily-update (runs the repo's per-day housekeeping skills and bundles their output into one PR). Also ships three PreToolUse Bash hooks: pr-template-guard (denies a gh pr create/edit whose body is missing a heading the repo's own PR template requires), skip-label-race-guard (warns when gh pr create applies the repo's review-skip label without --draft), merge-guard (warns, never denies, when a command merges a pull request), plus an opt-in PostToolUse hook, review-reply-postcondition (a review reply that claims a fix must name a commit reachable from HEAD). Reads.claude/maintainerd.json.
- Slug: repo-ops
- Publisher: Allen Hutchison
- Repository: https://github.com/Vycari/maintainerd
- Manifest: plugins/repo-ops/plugin.json
- Version: 0.6.13
- License: MIT
- Category (editorial): devops-cloud
- Skills: 5 (address-review, create-pr, daily-changelog, daily-update, release)
- MCP servers: 0
- Stars: 3
- Repository created: 2026-06-28
- Repository last pushed: 2026-10-08
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/repo-ops
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What repo-ops does, in the publisher's words

The baseline PR and changelog flow: the things you do on every repo, extracted so they behave the same on all of them. Nothing here merges.

This plugin used to ship a code-review skill. It was dropped in favour of Claude Code's built-in /code-review, which covers the same ground and avoids two plugins claiming the same command name. Point the built-in at config.guidelines.coding /.testing for this repo's specific standards: the built-in supplies the method, your guidelines supply the rules it can't know.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/Vycari/maintainerd/HEAD/plugins/repo-ops/README.md

## Skills

- 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 (i…
- create-pr: Create a pull request for the current repository the right way, enforce the repo's PR template, run every CI gate (format, lint, build, typecheck, tests) locally before pushing, require docs updates for user-facing changes, and write an honest, non-marketing PR body. Use whenever the user wants to…
- 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 <dat…
- 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 ask…
- 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 GitH…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
