Loading...
Loading...
Found 2,521 Skills
Sync local skills and references from the GitHub repo. Triggers on update skills, sync skills, 更新技能, 同步技能
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.
Manage stacked branches and pull requests with the gh-stack GitHub CLI extension. Use when the user wants to create, push, rebase, sync, navigate, or view stacks of dependent PRs. Triggers on tasks involving stacked diffs, dependent pull requests, branch chains, or incremental code review workflows.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
current release-driven profileでLinearをrelease planning / health / portfolio Practiceとして使い、GitHub execution stateとのcanonical ownershipを保ってreconcileする時に使用する。
Use when the user asks to list, show, or review open issues — from the tracker recorded in docs/agents/issue-tracker.md, whether GitHub, Jira, local markdown, or another backend, or from a repository or project the user names. Read-only: not for creating, editing, closing, or triaging issues.
[user/auto] 기존 GitHub PR 본문 또는 지정된 댓글에 로컬 이미지·GIF·MP4를 첨부합니다. 명시적 미디어 요청이나 정확한 근거 인계에만 사용합니다.
Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.
Turn customer feedback (usually an email) into discrete GitHub issues. Checks for duplicates, proposes new issues for approval, creates them, and drafts a reply email.
Turn your recorded calls into a go-to-market knowledge base: each recorded call is collected every morning, scribed into a log entry, and, once a claim repeats, promoted into context, as one pull request against your go-to-market repo. Nine recorders ship; a tenth is one adapter file. Triggers: "our call recordings never make it into the knowledge base", "turn our call transcripts into context", "we relearn the same objection every quarter", "scribe yesterday's calls into the repo every morning", "replace the GitHub Action that summarizes our meetings", "we record on Granola, not Avoma". Cargo project, defineAgent, harnessSlug claudeCode, workspace env var, GitHub, Avoma, Granola, Fathom, Gong, Fireflies, Grain, tl;dv, Modjo, Clari Copilot, cadence, context. Skip when: you want one call summarized right now, which is a read against the recorder's own API and needs nothing deployed.
Orchestrate AI-assisted software delivery across project bootstrap, requirement discovery and evolution, change proposals, technical design, GitHub milestones and issues, implementation, bug fixes, knowledge synchronization, changelogs, and finalization. Use when a repository needs a coherent engineering lifecycle, traceable specifications, current technical knowledge, or durable implementation history. Apply proportionately to the requested operation; ordinary small edits do not require a full lifecycle ceremony.