Loading...
Loading...
Found 2,510 Skills
project固有のstack・framework・runtimeに合わせてquality gateと動作確認レベルを設計・実行・更新する時に使用する。
Open a pull request or rewrite its description, with a one-sentence why, reviewer notes, and a visual change outline. Use whenever a pull request is opened or its description changes.
Configura um repositório para o pipeline: issue tracker e vocabulário de labels, a seção `## Commands` (lint/typecheck/test/build/clean) que o implementer lê como gate, a seção `## Fluxo` com as saídas recomendadas depois de um grill, o remote, o template de PR, a CI com esses gates e `npm audit`, os rótulos de risco e o `review-rules-projeto.md`. Rode uma vez por repositório, antes do primeiro uso de to-spec, to-tickets ou implement. Use quando o usuário disser "setup do projeto", "setup-project", "configura o tracker", "prepara o repo para o pipeline" ou variações.
Scout a single open-source project for contributions likely to be merged. Investigate candidate contributions (open good-first-issue / help-wanted issues, low-risk docs / test / small-feature work, areas with a precedent of merged AI-authored PRs), prepare a high-level plan for the top candidate(s), evaluate feasibility (merge likelihood, effort, prerequisites, maintainer norms / CI expectations), and post the result as a comment on the Multica sub-issue that scopes the project. Use whenever a sub-issue asks to "investigate potential contributions" in one project, or to "scout <owner/repo> for contributions". Investigation and planning only — never fork the repo, make code changes, or open a PR.
新規参入者が会話履歴や個人環境に依存せずprojectを理解・起動・検証・開発開始・作業復旧できるdocumentationを初期化・更新する時に使用する。
This skill should be used when the user asks about cross-platform electrobun support, "electrobun Linux", "electrobun Windows", CEF requirements by platform, "electrobun platform differences", or is setting up multi-platform CI for an electrobun app.
This skill should be used when the user is building electrobun features for the milady-ai/milady project, submitting PRs to milady that will be reviewed by the agent-review system, asks about "electrobun milady", "milady electrobun PR", trust tiers, Biome compliance, or the release-electrobun.yml workflow.
Review and resolve open review feedback on a pull request against its upstream repository, then keep the branch in sync without rewriting history. Use when asked to "review my PR", address PR/review comments, respond to reviewer feedback, resolve review threads, or sync a feature branch with upstream before review. Covers: resolving the upstream remote (from git remote -v when not configured), challenging vs. fixing each comment, replying to and resolving threads with gh, and detecting/handling a branch that is behind upstream main (conflict check, user confirmation, no force-push).
Stack draft PRs for the tickets a still-open PR unblocks — the frontier computed as if that PR were merged, branched on its head — and hand each to Copilot. Use when the user wants to start tickets blocked by an open PR, delegate the issues a PR will unblock, or open stacked PRs on top of a PR.
Checks if a community pull request is ready for human review. Verifies CLA signature, PR title format, description completeness, test coverage, and cubic-dev-ai issues, then triages to the right Linear team or recommends a close. Use when given a PR number or branch name to review, or when the user says /community-pr-readiness-check, or asks to check if a PR is ready for review.
Report stale git branches with a keep, archive, or delete recommendation, and propose enabling delete-branch-on-merge. Use for "clean up stale branches", "delete merged branches", "delete branch on merge", "which branches are dead", or /branch-cleanup. Checks age, author, ahead/behind counts, merged status, open pull requests, and ruleset protection, then prints exact deletion commands that require explicit per-batch authorization before any push. Do NOT use for local git worktree management (worktree add, list, or prune) — that stays out of scope. One-time repository merge defaults and branch-protection rulesets belong to /gh-bootstrap; this skill reads and reports on that state but does not set it up.
Use when the user wants several open issues built by agents and turned into pull requests — "work through the issues", "implement the open issues", "clear the backlog", "open PRs for #12 and #15" — optionally at an effort level ("/implement-issues low", "at medium effort"), and when plan pull requests it opened are approved or have comments to answer. Works in Claude Code, Codex, or any agent that can dispatch subagents. Not for one issue the user is building themselves in this session.