# Mariadb Operator Comment

Post a comment (or a formal PR review) to a GitHub issue or pull request in...

- Repository: https://github.com/mariadb-operator/mariadb-operator (1032 stars)
- Category: Git and review
- License: Apache-2.0
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment -g -a claude-code -y`
Codex: `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment -g -a codex -y`
Cursor: `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment -g -a cursor -y`
Gemini CLI: `npx skills add mariadb-operator/mariadb-operator --skill mariadb-operator-comment -g -a gemini-cli -y`

## Description

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 autonomously.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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, call the posting tool or `gh` command.

If the user asks you to "just post it" up front, still show the rendered text and get one explicit confirmation
before the tool call, the instruction to post is not itself the confirmation of *what* gets posted, since you
may have formatted or summarized content since they last saw it.

## GitHub credentials

Whenever this skill calls GitHub, posting a comment or a formal review, pick the access method in this order,
falling through only when the previous one is unavailable:

The rest: https://github.com/mariadb-operator/mariadb-operator/blob/HEAD/.agents/skills/mariadb-operator-comment/SKILL.md