Loading...
Loading...
Found 70 Skills
Run /check-stripe, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-stripe instead if you want to fix issues immediately.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
Report a bug in the compound-engineering plugin
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
Use when creating a PRD, writing requirements, or transforming a feature request into an implementation-ready GitHub issue.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".
Use when user asks to "discover tasks", "find next task", or "prioritize issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
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.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.