mariadb-operator-pr-review
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-pr-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# mariadb-operator PR Review You are a maintainer of mariadb-operator performing an initial review of a pull request. Evaluate the PR for correctness, safety, pitfalls, backwards compatibility and code quality, then give an overall assessment. ## AGENTS.md is the source of truth **Read `AGENTS.md` at the repository root before reviewing.** It is the authoritative description of this project's architecture, patterns, gotchas and guardrails. This skill deliberately does **not** restate those rules — it tells you *how to run a review that checks a diff against them*. Throughout, "§ <name>" refers to a section of AGENTS.md. When a check below says "verify against § X", open that section and compare the diff to it. ## GitHub credentials Whenever this skill calls GitHub — fetching PR context or delivering a review — pick the access method in this order, falling through only when the previous one is unavailable: 1. **Project-scoped GitHub MCP tools** (names like `mcp__github-mariadb-operator__*`). These may show up as deferred tools — if so, load their schema with `ToolSearch` (e.g. `ToolSearch({query: "select:mcp__github-mariadb-operator__get_file_contents", max_results: 1})`) before cal
- AGENTS.md is the source of truth
- GitHub credentials
- Step 0 — Gather context
- Step 1 — Triage
- Step 2 — Evaluate five dimensions
- A. Correctness
- B. Safety
- C. Pitfall detection
- D. Backwards compatibility
- E. Code quality
- Step 3 — Verdict
- What not to flag
- Delivery
- Output format
gh pr view <n> --json title,body,author,state,additions,deletions,files,labels,baseRefName gh pr diff <n> # full unified diff gh pr view <n> --json reviews,comments # existing review discussion git fetch origin <baseRefName> git show origin/<baseRefName>:<path/to/file.go>
What does the mariadb-operator-pr-review skill do?
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".
How do I install it?
Run `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-pr-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mariadb-operator/mariadb-operator, a repository with 994 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
