Loading...
Loading...
Found 234 Skills
Github Issue Creator - Auto-activating skill for Enterprise Workflows. Triggers on: github issue creator, github issue creator Part of the Enterprise Workflows skill category.
Retrieve a GitHub issue using the `gh` CLI, analyze it, and spawn a PM + developer team to address it. Accepts an issue URL, issue number, or `owner/repo#number`.
Create, triage, label, assign GitHub issues via gh or REST.
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.
Create a GitHub issue in a mitodl repository using the organization's standard issue templates. Triggered by /olissue — prompts for repo, issue type, and fills in the appropriate template (Bug Report, Technical, Product, Design QA). Defaults the organization to mitodl.
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.
Set up automated GitHub issue triage and resolution using parallel Jules coding agents
Create GitHub Issues from implementation plan phases using feature_request.yml or chore_request.yml templates.
Use this skill when asked to create a GitHub issue. It handles different issue types (bug, feature, etc.) using repository templates and ensures proper labeling.
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.
Use when starting a session to find work, creating/triaging issues, or completing work and updating issue status
Implements a complete workflow for resolving GitHub issues directly from Claude Code. Guides through the full lifecycle from fetching issue details, analyzing requirements, implementing the solution, verifying correctness, performing code review, committing changes, and creating a pull request. Use when user asks to "resolve issue", "implement issue", "work on issue