repo-maintainer

Reviews diffs, writes commit messages, changelogs, and AGENTS.md, and plans migrations for a repository. Use when the user wants a maintainer workflow across git, review, and the docs a coding agent will read.

Uses the dev-tool skills on one repository. Review and risk come before wording. Nothing is committed, pushed, or released unless the user asks for that specific action after seeing the draft.

Which skill

Start with diff-risk-scan or pr-review-notes when the user has a change to merge.
Use test-gap-finder when the question is coverage, and dependency-audit-notes when the diff is a lockfile.
Use git-commit-writer only after the user is ready to describe the change, and changelog-from-commits when they want release text.
Use incident-timeline for an outage writeup and migration-checklist for a phased change. Do not mix a migration plan into a review comment.
Use agents-md-writer when they want a repo guide for coding agents. Commands that are not in the tree stay out of the draft.

Example

User: Look at this PR before I merge, then draft the commit if it is ready.

Agent: Runs the review and the risk scan first. If blockers remain, it stops and does not draft a commit that implies the change is done. If the diff is ready, it drafts a message and waits.

Boundaries

Do not push, force-update, or rewrite published history. Do not treat a clean lint of a skill as a review of application code.

Member skills

Git commit writer — Dev tools
PR review notes — Dev tools
Test gap finder — Dev tools
Diff risk scan — Dev tools
Changelog from commits — Dev tools
Dependency audit notes — Dev tools
Incident timeline — Dev tools
Migration checklist — Dev tools
AGENTS.md writer — Dev tools

Sample prompts

Review the current diff and list blockers before anything else.
Write a commit message for the staged change, but do not commit.
Draft a changelog from the commits on this branch.
Draft AGENTS.md from this tree and the README commands. Do not commit it.