Loading...
Loading...
Found 163 Skills
Turn a GitHub issue into an implementation plan — investigate the codebase, propose an approach, list critical files and changes, outline test strategy. Use when user says 'plan this issue', 'what's the approach for', 'how would I tackle', 'implementation plan for', or 'before coding'. Do NOT use for actually implementing (write the code directly after the plan) or for breaking a too-large issue into sub-issues (use splice-issue).
Create GitHub Issues with a parent-child structure (sub-issues). Generate parent and child issues using `gh issue create`, and link the parent-child relationship with `gh api .../sub_issues`. It is recommended to use Conventional Commits format (`feat:`, `fix:`, etc.) for titles. Used for scenarios like "Create an Issue" and "Break down tasks into Issues".
Orchestrate same-repository GitHub issue work from branch setup through local review and PR readiness. Use when the user invokes `/develop-issue #123`, `/develop-issue https://github.com/<owner>/<repo>/issues/123`, or asks to develop exactly one issue end to end.
Use this skill to triage a single newly opened, reopened, or `status/needs-triage`-labelled issue in microsoft/apm. Emit one synthesized comment with a triage decision, label set, milestone, and suggested next action.
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
GitHub Discussion CLI for AI agents. Turn-based conversations on GitHub issues between Claude Code, Codex, and other agents.
Review and process app submissions for the Pollinations showcase. Parse issues, validate submissions, create PRs, handle user corrections.
[Fix & Debug] ⚡⚡ Fix a GitHub issue with systematic debugging
Run /check-onboarding, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-onboarding instead if you want to fix issues immediately.
GitHub issue state machine and code integration patterns. Covers state transitions (needs-triage → accepted → in-progress → completed), branch naming (feat/123-desc), PR linking (Closes
Create structured GitHub issues from conversation context using gh CLI
This skill should be used when the user asks to "create an issue", "file a bug", "create a feature request", "open a GitHub issue", "report a bug", "request a feature", "create a task", "break this into issues", or describes a feature/bug they want tracked in GitHub. Guides interactive issue creation with structured templates, workspace change attachment, and optional autonomous label for the automated pipeline.