Mariadb Operator PR Review
Perform a structured maintainer-style PR review for the mariadb-operator repository.
Install
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-pr-review -g -a claude-code -y- Repository
- mariadb-operator/mariadb-operator1k
- Category
- AI and agents
- Updated
- 10d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
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".
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:
- Project-scoped GitHub MCP tools (names like
mcp__github-mariadb-operator__*). These may show up as deferred tools, if so, load their schema withToolSearch(e.g.ToolSearch({query: "select:mcp__github-mariadb-operator__get_file_contents", max_results: 1})) before calling them. ghCLI with the project-specific token, if themariadb-operatorMCP server isn't connected. UseGITHUB_MARIADB_OPERATOR_TOKENexplicitly (GH_TOKEN="$GITHUB_MARIADB_OPERATOR_TOKEN" gh ...) rather than the ambientgh authsession.- Generic GitHub MCP tools (
mcp__github__*), if neither of the above is available. ghCLI with default credentials (plaingh auth, no explicit token) as the last resort, if none of the above work.
Step 0, Gather context
Given a PR URL or number, collect it via the access method chosen in the GitHub credentials
section (the gh invocations below assume that method, add the GH_TOKEN override or swap in the equivalent
MCP tool as appropriate):
