Loading...
Loading...
Found 90 Skills
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
Triage and resolve repository GitHub issues using the bundled CLI. Use when asked to read issue state, discuss issue scope, implement issue-driven code changes, post comments, or close issues.
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
Create or update GitHub issues with template detection, title formatting, and assignment/label safeguards. Use when the user wants to file a bug, request a feature, create a tracking issue, or edit issue details.
Use when starting a session to find work, creating/triaging issues, or completing work and updating issue status
Create, triage, label, assign GitHub issues via gh or REST.
Crée, récupère, met à jour et gère les issues GitHub avec collecte complète du contexte. À utiliser quand l'utilisateur veut créer une nouvelle issue, voir les détails d'une issue, mettre à jour des issues existantes, lister les issues du projet, ajouter des commentaires ou gérer les workflows d'issues dans GitHub.
End-to-end orchestrator that turns findings from ANY input (audit spreadsheet, code/security review, QA report, meeting notes, a pasted list of issues) into a GitHub Issues backlog with a milestone, labels, and a tracking issue. Drives the sibling github-backlog skills in order with safety gates. Trigger whenever the user says "turn this audit/spreadsheet/review/list of issues into GitHub issues", "create a backlog from these findings", "file these as GitHub issues", "import this xlsx/csv into GitHub", "make issues from this report", or hands you a source document and asks for it to land in GitHub. This is the headline, one-shot entry point (/github-backlog:run wraps it). Not for editing existing issues individually.
Map triaged findings to GitHub Issues with the correct labels, milestone, and body, and emit github_backlog_input.json ready for creation. Use this AFTER triage and BEFORE creating issues — when the user asks "what labels should these get", "turn these findings into GitHub issues", "classify these for GitHub", or "build the github backlog input". Maps severity to priority labels (P0-P3), kind to type labels (bug/enhancement/task), and hours to size labels (size:XS-XL). Creates a milestone for the batch. Hands off to github-create-issues.
Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.
Set up automated GitHub issue triage and resolution using parallel Jules coding agents
Create GitHub Issues from a github_backlog_input.json (the output of classify-github-issues) via the bundled create_github_issues.py script. Always shows a visual dry-run table first and only creates real issues after the user explicitly approves. Use this whenever there is a github_backlog_input.json or any file of items to file in GitHub, or when the user says "create these GitHub issues", "file the backlog", "push these to GitHub", or "create the issues". This is the step that actually writes to the repo, so prefer it over hand-rolling API calls. After creating, it writes github_backlog_result.json for github-writeback-tracking.