mariadb-operator-comment
Post a comment (or a formal PR review) to a GitHub issue or pull request in mariadb-operator/mariadb-operator. Use whenever the user wants to publish something to GitHub for this repo — "comment on issue #123", "post this as a PR comment", "leave a note on #456", "reply on the PR" — and especially when they want the output of the mariadb-operator-pr-review skill delivered to GitHub instead of just shown in chat, e.g. "review PR #1234 and post it as a comment" or "post the review results to the PR". Always confirms the exact comment text with the user before publishing — never posts autonomousl
npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment --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 Comment Publish a comment or PR review to `mariadb-operator/mariadb-operator` (or another repo the user names). This skill only handles *delivery* — if the content is a code review, run `mariadb-operator-pr-review` first (or use its output if already produced in this conversation) and pass the result in here for formatting and posting. ## Never post without confirmation **This is the one rule that matters more than anything else below.** Posting to GitHub is public, hard to fully undo (edits and deletions leave an audit trail, and people may already have read a notification), and visible to the whole team. Before calling any tool that actually publishes something: 1. Render the exact text you are about to post, in full — not a paraphrase or a summary of it. 2. State exactly where it's going: `owner/repo#number`, and whether it's a plain comment, a review comment, or a formal review (with its verdict, e.g. "Request changes"). 3. Ask the user to confirm with `AskUserQuestion` (options like "Post it" / "Edit first" / "Cancel"). Treat silence, an ambiguous reply, or moving on to a different topic as "no" — do not post speculatively. 4. Only after an explicit go-ahead
- Never post without confirmation
- GitHub credentials
- Step 1 — Resolve the target
- Step 2 — Assemble the comment body
- Step 3 — Pick plain comment vs. formal review
- Step 4 — Show the user exactly what will be posted, then stop and ask
- Step 5 — Post
- What this skill does not do
gh issue comment <n> --repo mariadb-operator/mariadb-operator --body "<text>" gh pr comment <n> --repo mariadb-operator/mariadb-operator --body "<text>"
What does the mariadb-operator-comment skill do?
Post a comment (or a formal PR review) to a GitHub issue or pull request in mariadb-operator/mariadb-operator. Use whenever the user wants to publish something to GitHub for this repo — "comment on issue #123", "post this as a PR comment", "leave a note on #456", "reply on the PR" — and especially when they want the output of the mariadb-operator-pr-review skill delivered to GitHub instead of just shown in chat, e.g. "review PR #1234 and post it as a comment" or "post the review results to the PR". Always confirms the exact comment text with the user before publishing — never posts autonomousl
How do I install it?
Run `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment --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.