Loading...
Loading...
Found 2,042 Skills
Run the software factory. Use when the user types /factory alone or /factory help (prints the help), /factory
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.
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.
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.
Draft, edit, review, and refine all human-facing writing, from short-form copy to connected prose. Use it whenever readers must follow ideas, context, reasoning, narrative, or tone. Use it across technical surfaces such as package and repository descriptions, README and technical document content or information architecture, CLI wording, JSDoc and docstrings, explanatory source comments, runtime messages, test titles, labels, and repository collaboration through issues, pull requests, and Discussions. Do not use for LICENSE text, formatting-only work, or tasks that neither evaluate nor change wording or information architecture. Agent responses are not a trigger on their own.
Routes questions about the Cursor Origin API to the right section of the Origin docs and names the few rules to check first. Use when a task mentions Origin, the Origin API, Origin Apps, or Origin webhooks, including creating an Origin App, authenticating as one, calling Origin endpoints, or handling Origin webhook deliveries.
Use when creating or updating a PR in the kimi-code repository: how to write each section of the PR template concisely so that reviewers can easily understand it, including the "Behavior Changes and Affected Users" table.
application / serviceのenvironment secretをInfisical中心で設計・初期化・移行・検証する時に使用する。CLI-first、repository-controlled schema、Machine Identity、GitHub OIDC、agent least-privilege、secret-safe evidenceを扱う。
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.