Loading...
Loading...
Found 2,056 Skills
Monitor a pull request through review and CI. Use when the user asks to monitor, watch, or babysit a PR.
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.
Commit changes and create a pull request to the official upstream repo
Draft and submit one high-quality Nexus idea for a Propose / ProposalScout dispatch action. Use when the action prompt names skill nexus-proposal-scout or route ProposalScout.
Write a branch's PR body that tells a reviewer how much attention it needs, with a visual summary, harvested evidence and a fresh-context one-way or two-way door call, then put it and an attention label on the branch's PR. Use when a branch is ready for review, when the user says "write the PR body", "update the PR description", "how risky is this PR", or "is this ready to merge", and when another skill closes a branch.
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.
Install, discover, remove, and update agent skills using the npx skills CLI. Use when asked to install a skill, add a skill from a repo, find or search for skills, list installed skills, remove or uninstall a skill, update skills, or check for updates. Triggers on: "install X skill", "add the Y skill", "find skills for Z", "what skills are available", "remove skill", "update my skills", "check for skill updates", "search for a skill that does X".
This skill should be used when a designer wants to produce a holistic design for a full feature before it is broken into tasks — for example "design feature
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
Track Remotion CI flakes in issue
Viewer release-notes overstack TỨC THÌ (kiểu /release-notes của Claude CLI). Gõ /ovs-notes → liệt kê NGAY changelog OVERSTACK framework (newest-first) để chọn & đọc; /ovs-notes <version|latest> in đầy đủ; /ovs-notes --here = release của PROJECT hiện tại. READ-ONLY, KHÔNG side-effect — KHÁC /ship (quy trình CẮT release). Trigger: /ovs-notes, 'xem release notes', 'release notes bản nào', 'changelog', 'các bản đã ra', 'bản mới nhất có gì'.
Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request description as before/after tables, and upload them with `gh --attach`.