Loading...
Loading...
Found 236 Skills
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.
Fixes GitHub issues from a provided issue URL. Creates a feature branch, implements the fix, updates docs and agent skill when needed, and opens a pull request. Use when given a GitHub issue link or asked to fix/resolve an issue and create a PR.
Fetch a GitHub issue by number or URL, analyze its scope of work, cross-reference local project docs and repo instruction files, check blocking relationships, and produce a structured implementation analysis with a task list.
Turn vague intent into a precise, executable spec in five phases. (gstack)
Review whether a GitHub issue is complete enough for its current stage and decide the next PR or closure action. Use before PR, before closing an issue, after merge, or when auditing a closed issue for regressions or missing scope. For pre-PR checks, use CodeRabbit CLI review; when an open PR exists and corrective review work is needed, use autofix.
Migrate field values from GitHub Project V2 fields or repo labels to org-level issue fields. Use this skill when users need to bulk-copy metadata (priority, status, dates, text, numbers) from project fields or labels to issue fields, or when they ask about migrating, transferring, or copying project field data or labels to issue fields.
Propose improvements to a skill in its canonical repository. Defines how to proceed when work does not follow the skill, when information obtained through Web searches differs from or is newer than the skill's content, or when strictly following the skill's conditions is judged to prevent the best possible result. Includes guidance on not directly editing skills installed in the home directory, routing proposals to the appropriate repository, and Issue title and body templates. Use this when you have questions about a skill's content or want to propose an improvement to it.
This skill should be used when handling issue intake rotation duties for the Positron repository. It provides workflows for reviewing and organizing new issues, responding to discussions, handling support tickets, and searching for related content. Use this skill when on intake rotation duty, when helping someone with intake tasks, or when learning the intake rotation process.
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
Report a bug in the compound-engineering plugin
Analyze a GitHub issue and create a detailed technical specification
Break a plan into tracer-bullet tickets with blockers and publish via issue-tracker. Local files only if asked.