Loading...
Loading...
Found 2,510 Skills
Implement a chosen contribution in a fork of an open-source project: verify the user's fork already exists (stop and ask the user to fork if it does not), strictly follow the upstream repository's conventions (CONTRIBUTING.md, AGENTS.md, CLAUDE.md, PR template, commit and sign-off format), work on a branch of the fork without opening any fork PR, write equivalence-first tests, run the upstream CI/CD checks locally before pushing (the fork will not run them), sign commits per the upstream DCO/CLA convention, and post the PR body — built from the upstream PR template — in a markdown pasteable format on the Multica issue. In review iterations (the PR is already open and a maintainer left review comments), address only the explicit requests on the same fork branch and post a pasteable PR comment per PR in the same fenced-markdown format; PR discussions — replies, resolutions, ambiguous asks — are left for the humans. Use whenever a Multica issue asks to "work on the contribution", "implement <candidate> in <owner/repo>", "prepare the branch for <repo>", "turn the scouted contribution into a PR-ready diff", or to "address the review comments on <PR>" — even if the issue only names the target repo and the change to make.
Reviews a code diff (PR, branch, commit range, working tree, or a diff already in the conversation) in a fresh-context read-only subagent, because a session holding the conversation is a biased reviewer, posts its Conventional Comments findings inline and its APPROVE, REQUEST CHANGES, or COMMENT verdict to the pull request when one exists, and returns a short summary. Use when the user says "code review", or when asked to review code, a diff, or a PR, including a pasted diff, a .diff or .patch file, or a diff shown earlier; never review it inline. Not for design docs; use reviewing-design-docs. Not for a security-focused review; use reviewing-security.
Use for version bumps on explicit request or as the pre-merge step of a PR land. Never infer from finished, reviewed, green, or draft-ready work. Assigns SemVer.
Watches the user's own PR in a bounded loop, triaging new review feedback and reporting failing CI, or re-running or fixing it when granted, until approval, then hands off to landing-prs without merging, even when asked to merge once approved. Use when the user says "watch this PR", or when the user explicitly asks to watch their PR for feedback or CI, including a watch that should merge on approval. Never infer from an open PR. Not for a PR the user reviewed; use watching-reviewed-prs.
Watches a PR the user reviewed in a bounded loop, re-reviews each settlement of their feedback against the branch, resolves or rebuts, and approves once every item settles. Use when the user explicitly asks to watch and approve a PR they reviewed. Not for the user's own PR; use watching-authored-prs.
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.
The domain expert's product manager in a project repository run by the Boring Factory. Use when the expert brings a need or an idea, wants to clarify, change or resume a feature ("reprends la fiche"), asks what is happening with a feature, has a builder's question to answer, or has a preview to try and accept. Interviews one question at a time, writes the contract and mockups on the contract pull request, and submits the expert's approval only after the expert confirms. Never writes code.
User-triggered Enterprise PR recorder for a completed phase. Stacked plans publish their phase branch through the publish-phase repair command; other plans create or reuse the current-branch PR. Links the tracked issue and records PR identity. It never posts review verdicts, never rebases, and never force-pushes.
Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins. Use for pipelines and releases, not gameplay implementation or server operations.
Roda o loop de implementação — implementar → revisar → corrigir → re-revisar — sobre uma unidade de trabalho, e abre branch e PR ao final. Aceita uma issue com ready-for-agent, uma SPEC (com ou sem tickets), um caminho de arquivo, ou o entendimento acordado num grill. Use: /implement 12, /implement (após um grill), ou sem argumento para escolher entre as issues prontas.
Files a short, clear pull request for the current branch. Use when the user asks to open, file or create a PR, or says /ds-pr.
Pull request: use when a PR needs opening, or commits sit on main and need moving to a named branch.