maintainer-review

Solid

Review someone else's pull request as the maintainer deciding whether it merges — every prior comment walked, every claim verified, and nothing posted without your go-ahead.

AI & Automation 40 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
54
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Maintainer review You are the merge gate, not the author's assistant: the question is whether this ships, and the contributor will argue back. Review in **this** session, not a subagent. A session opened for the PR is fresh already, and staying in it keeps the diff, the comments and your findings in hand for the argument that follows. Session already loaded with unrelated work, say so and offer a fresh one first. ## 1. Gather Take a PR reference on any forge and pull, through whatever tooling is connected, **all** of it before judging: metadata (title, description, author, base and head refs, draft state, labels, mergeability, required-check results), the diff, and every comment stream — conversation comments, review verdicts with their bodies, and inline threads with their replies. A single "view PR" call typically misses the review bodies and the inline threads; expect one request per stream. Fetch here, never via a review-capture skill: those write the author's triage file and take thread status from the forge, which step 3 re-derives against the current head. Fetch, then diff the merge base — `<base>...<head>`, three-dot — so the target's own commits don't read as the author's. A fork's head has no local ref; fetch the forge's PR ref for it. Done when the head SHA, the base, the diff, the check results and all comment streams are in hand. ## 2. Follow every reference Extract every issue and PR reference, commit sha, external link and domain identifier (a ticket ...

Details

Author
eai-org
Repository
eai-org/agent-toolkit
Created
2 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

GitHub · DevTools

Bundled in these plugins

agent-toolkit

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

pr-review

Pre-landing PR review. Analyses the current branch diff against the base branch for structural issues — SQL safety, LLM trust boundary, race conditions, shell injection, enum completeness, scope drift. Domain-agnostic. Adapted from Garry Tan's gstack /review (garrytan/gstack); role-catalog framing stripped; MARVIN's REVIEW.md honoured.

2 Updated 5 days ago
RobertIlisei
Code & Development Listed

review

Use before merging to verify completed work meets requirements and quality standards. Dispatches code-reviewer for holistic assessment of the full git diff against the original plan.

2 Updated 4 weeks ago
nicodiansk
Code & Development Listed

pr-review

Reviews a merge/pull request against its linked tracker ticket, then posts inline comments on the diff for you to submit — it fetches the change and ticket context, structures the review, and writes the comments directly to the host's draft/pending-review mechanism. Ships with adapters for GitLab and GitHub as the code host, and JIRA and GitHub Issues as the tracker, but degrades gracefully to any other host or tracker reachable via tool discovery. User-only: runs only when explicitly invoked with /pr-review <MR or PR URL>. When the user wants to review a GitLab MR or GitHub PR, code-review a merge/pull request, or evaluate a change's diff against its linked ticket, suggest running this command rather than doing a manual review.

0 Updated today
azborgonovo