В каталоге 185 367 навыков в 14 категориях.
GitHub 이슈 기반 기능 구현 스킬. 현재 브랜치의 이슈를 확인하고 DDD → Plan → TDD → Test 파이프라인을 실행합니다. 사용 시기: (1) feature 브랜치에서 작업 시작 시 (2) 이슈 기반...
Analyze a Jira ticket into an actionable breakdown, following linked tickets and Confluence context to surface gaps and...
Fetch and analyze GitHub issues from the monorepo. Use when user asks about issues, what's blocking, issue status, depen...
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) an...
Create and label GitHub issues (including epics) for kajet-turbo following the project's established conventions — title...
Enforce Issue-First pattern by creating Beads tracking issue BEFORE implementation. MUST BE USED for all implementation...
Fix a tracked security issue in a public `<upstream>` PR: sync the tracker, propose a plan, and on confirmation write th...
ユーザーが「Issue #N を解決」「Issueを解決して」「Issue を fix」等と要求した時に使用。 GitHub Issueの完全な解決ワークフローを自動実行。 Issue分析、テストファースト開発、最小限の修正実装、PR作成ま...
Create a GitHub issue from an approved plan before implementation
Group similar issues.
特定の GitHub issue への実装着手と PR 作成を依頼されたときに使う。issue 番号・URL・会話内で選んだ issue のいずれかを起点に、runtime と worktree の実装隔離を preflight で保証して...
This skill should be used when the user asks to "implement task", "claim task", "work on task", or mentions implementing...
Orchestrates issue implementation with automatic review and commits. Use when asked to "implement feature", "implement e...
This skill should be used when the user asks to "create implementation plan", "plan the implementation", "detailed plan"...
Reviews code changes from a completed task implementation for correctness, completeness, and simplicity. Use when asked...
Import new `<security-list>` reports into `<tracker>`: find threads not yet tracked, propose the imports (default: impor...
Open one or more `<tracker>` tracking issues from a markdown file containing a batch of security findings. Each finding...
Open a tracker for a security-relevant fix that already exists as a public `<upstream>` PR, with no `<security-list>` re...
Triage a security scanner's multi-finding output (via a scan-format adapter; ASVS is the reference), bucket each finding...
Sub-skill for reports relayed onto `<security-list>` by a broker (the ASF security team, a disclosure platform, a SOC) r...
Issueの初期トリアージスキル。Issueを受け取り、標準化された分析結果(分類・深刻度・影響スコープ・不確実性・次アクション参照)を生成する。GitHub/Jira/Linear等のトラッカーからissue_payload形式で受け取る...
Use when filing an approved task spec as a GitHub issue with a local archive and optional worktree implementer. Don't us...
Turn a noisy inbound request into a bounded intake artifact and an explicit next runx lane.
Close a tracker as invalid: label, closing comment, board archive, and — for `<security-list>` imports — a polite-but-fi...
GitHub issue を起点に、PR や永続的な repo 変更を成果物としない調査・設計・技術検証を実行し、構造化した結果を issue コメントへ記録して受け入れ条件確認後に close する。Ready なコメント完結型 issu...
Create relationships between issues via comment references
Relate GitHub issues and PRs — pick the right edge type (blocked-by via GraphQL, parent/sub-issue, Closes/Fixes in PR bo...
List and filter tickets/issues from configured backend
Create a well-formatted local report for a provided list of issues.
オープン Issue の一覧を優先順位付きで表示する。「Issue 一覧」「Issue リスト」「オープン Issue」「Issue を見せて」「チケット一覧」「未解決 Issue」「Issue 確認」などで起動。優先度順にソートして表示。
Provides guidance for systematically logging issues during Ralph autonomous execution. Use when: (1) Any problem occurs...
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan featu...
Use for GitHub Issue searches, plan saving, creation and updates, Sub-issues, follow-up requests, writing or updating Is...
Manage GitHub Issues 2.0 relationships with gh CLI: parent issues, sub-issues, blocked-by, and blocking links.
Work with GitHub issues - create, list, update, comment, and search issues using gh CLI
Issue作成・分類・管理のガイドライン、テンプレート、ラベル運用、ライフサイクル管理を定義する。Issue作成時、バグ報告時、タスク管理時、またはユーザーがIssue、バグレポート、タスク管理、ラベル運用、Issueテンプレートに言及した...
This skill provides procedures for creating and managing GitHub issues. All issues MUST use standardized templates and f...
议题管理工具。从代码审查报告创建 GitHub Issues,跟踪和修复问题,管理技术债务。用于将审查结果转化为可执行任务、讨论特定问题、批量修复 issues。触发词:创建议题、管理 issue、修复问题、讨论 issue。
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull reque...
Create and draft markdown-based issue documents (bug reports, feature plans, RFCs, ADRs, tasks, retrospectives) in the t...
Use when a human asks to compare one closed or stale tracker issue with current reality and mark it done or update it. D...
Use when orchestrating a Jira issue through the full development lifecycle to Harness PR with branching, commits, and do...
Use when the user has NOT yet decided which registered issue to work on and needs help choosing. This is the pre-decisio...
Start working on GitHub issue with deep-dive workflow (research, innovate, plan phases)
Guide structured analysis of problems and planning of implementation. Use when starting work on a new feature, encounter...
Use to select and advance one eligible issue from an authorized pool through claim, review, release, and live verificati...
現在のブランチでPull Requestを作成し、CIステータスを確認。「/issue-pr」で使用
Preflight a tracker issue, linked change, or branch-scoped work reference before implementation; stop with a tracker dra...
Automatic GitHub issue progress updates from commits and sub-task completion. Use when tracking issue progress from comm...
Create or edit a GitHub issue with `gh` from the reviewed draft at `.github/drafts/issue-draft.md`. Use only when that d...
Review tracker issue readiness before implementation and draft the appropriate no-mutation tracker update.
既存の GitHub issue を `issue-create` skill のフォーマットに沿って整理する。タイトルのみで起票された issue や、フォーマット不完全な issue を後から rich plan に仕上げ直したい場合に...
open な子が全部ブロッカー待ちで止まった親 Issue を、子を他の親へ移して close する。「issue-regroup」「親issueを閉じられるようにして」「子を付け替えて」と指示されたとき。
Slash command to evaluate whether an issue or pull request is still relevant, actionable, and worth keeping open
只在用户明确要求提交 GitHub Issue、GitHub Bug Report 或 GitHub Feature Request 时使用。用户只说“提交问题”“提交反馈”“上报 bug”“这是个 bug”或描述功能建议但未点名 GitH...
作業進捗をGitHub issueに自動報告します。計画立案時、知見獲得時、問題発覚時にブランチ名からissue番号を抽出し、構造化されたコメントを投稿します。
Helps users report issues with GTM skills — incorrect advice, broken activation, missing context, or unexpected behavior...
GitHub 이슈 해결 워크플로우. 분석 → 구현 → 검증 자동화.
Unified issue resolution pipeline with source selection. Plan issues via AI exploration, convert from artifacts, import...
Takes one triaged tracker issue to a fix by the right route: `quick-fix` for something small, the `feature-*` pipeline f...
Autonomous issue resolution agent that investigates, plans, and fixes issues using sub-agents and browser-based validati...
GitHub Issue resolver skill that analyzes, triages, and proposes solutions for issues with full SDD integrationTrigger t...
Review issues for completeness and dependencies
系統化的問題分析專家技能,自動協調五個專門代理進行深度問題分析。 適用於: - 使用者或 PM 報告的線上問題 - 開發團隊反映的技術問題 - 測試發現的 bug - 生產環境告警和異常
Reviews and categorizes GitHub issues by difficulty (easy/medium/hard). Use when you need to triage open issues, ask cla...
Review a GitHub issue the way /code-review reviews a PR. Fetches the issue with the gh CLI, checks the report against th...
Automatically reviews code changes against issue/spec at evaluate phase start to ensure implementation completeness
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de...
A pessimistic go/no-go the moment you pick up a GitHub issue — read it skeptically and hunt for reasons NOT to do it (al...
Search and list issues via Fractary CLI
Triage GitHub issues, bug reports, feature requests, and vague tasks into reproducible, scoped engineering work. Use whe...
Issue粒度判定とコード行数見積もりの基準、サイズラベル、分割判定ロジックを定義
Draft implementation-ready vertical tracer-bullet slices from a plan, PRD, audit finding, or Goal Contract. Adapted from...
大きすぎる/複数の関心事を含む既存 GitHub Issue を sub-issue に割り、親を umbrella に作り替える。「issue-split」「issueを分割して」「issueをsub-issueに割って」と指示されたとき...
DesignDoc の「Issue 構成」をもとに、Linear の実装 issue をリポジトリ単位で起票する。「issue を切って」「実装チケットを起票して」「/issue-split <DesignDoc URL or チケット>」...
Split complex issues into smaller, implementable sub-issues. Called automatically when ComplexityGate determines an issu...
Analyze a GitHub issue for mixed concerns and split it into focused sub-issues with proper cross-references. Integrates...
GitHub Issueの作業を開始する。ブランチを作成してチェックアウト。「/issue-start 4」のように使用
Show current work status
Suggest Jira components for one ticket or sweep a project's open tickets, confirming before any modification. Use when t...
Synchronize a security issue in <tracker> with the state of its GitHub discussion, the <security-list> mailing thread, a...
Mirror issues and status across issue trackers with stable external-ID mapping to avoid duplicates. Load when syncing Gi...
Automatically detect and update linked issues based on commits, artifacts, and task events
Keeps issues synchronized across multiple project management tools. Maps statuses, priorities, and assignees between Git...
Classify GitHub issues with visible high-level type labels such as feature, bug, change, or chore in addition to agent-a...
What should this skill be called?
Generate GitHub issue templates for bug reports, feature requests, and questions. Triggers on "create issue template", "...
Templates for creating well-structured GitHub issues for bugs, features, and tasks
Internal runtime support for universal skills that validate canonical scoped issue titles. Do not invoke directly.
Turn issues, bug reports, feature requests, and engineering tasks into implementation plans. Use when Codex is asked to...
Convert a .NET bug report or feature request into an ordered implementation plan with validation steps.
Use when an Issue, bug report, ticket, or scoped request must become a reviewable code change, test evidence, commits, a...
Implement one bounded repository issue with normal host tools, prove the tested change through one scafld finalize wall,...
Use this skill for turning issues into implementation plans, branches, code changes, tests, and PR descriptions. Trigger...
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, the...
GitHub Issue→実装タスク生成(Issue分析→タスク分解→チェックリスト作成)
Post a status comment on a GitHub issue (starting work, plan update, completed)
Pull issue/PR/ticket details from Jira, GitHub Issues, Linear, or Azure Boards via MCP into `01-spec.md` `## Source`. Us...
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress m...
Creates and manages issues via tissue for tracking work items, bugs, and features. Use for organizing work, checking rea...