๋ณธ๋ฌธ์œผ๋กœ ๊ฑด๋„ˆ๋›ฐ๊ธฐ
cccskills

mariadb-operator

@mariadb-operator

์กฐ์ง

๐Ÿฆญ Run and operate MariaDB in a cloud native way

์Šคํ‚ฌ 3๊ฐœ์ €์žฅ์†Œ 1๊ฐœ 1์ฒœ

์Šคํ‚ฌ(3)

๊ฒ€์ƒ‰์—์„œ ์ขํžˆ๊ธฐ

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

ํ•œ๊ตญ์–ด ์š”์•ฝ์€ ์ค€๋น„ ์ค‘์ž…๋‹ˆ๋‹ค. ์›๋ฌธ ์„ค๋ช…์„ ํ‘œ์‹œํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

mariadb-operator/mariadb-operator1์ฒœ2026๋…„ 10์›” 24์ผ ์—…๋ฐ์ดํŠธ

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/mariadb-operator1์ฒœ2026๋…„ 10์›” 24์ผ ์—…๋ฐ์ดํŠธ

Create the release notes and upgrade guide for a mariadb-operator release. Given the release PR whose body lists every PR included in the release, it gathers each PR, groups the changes by relevance, and produces `docs/releases/RELEASE_<version>_HEADER.md.gotmpl` and `docs/releases/UPGRADE_<version>.md` in the format the previous releases use, then opens a PR targeting `release-<version>`. If no release PR is provided it asks for the new version and infers the changes from git history since the last tag. Use whenever the user wants release notes, an upgrade/update guide, or docs for a new mariadb-operator version โ€” "create the release notes for 26.10.0", "write the upgrade guide", "document this release", "prepare the release PR docs" โ€” even if they don't mention a release PR.

ํ•œ๊ตญ์–ด ์š”์•ฝ์€ ์ค€๋น„ ์ค‘์ž…๋‹ˆ๋‹ค. ์›๋ฌธ ์„ค๋ช…์„ ํ‘œ์‹œํ•˜๊ณ  ์žˆ์Šต๋‹ˆ๋‹ค.

mariadb-operator/mariadb-operator1์ฒœ2026๋…„ 10์›” 24์ผ ์—…๋ฐ์ดํŠธ

๋ณธ์ธ ๊ณ„์ •์ธ๊ฐ€์š”? GitHub๋ฅผ ์—ฐ๋™ํ•˜๋ฉด ํฌ๋ฆฌ์—์ดํ„ฐ ํŽ˜์ด์ง€์— ๋ชจ์„ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค (์ผ๋ณธ์–ด)