Loading...
Loading...
Found 34 Skills
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
Run /check-landing, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-landing 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
Break a large GitHub issue into independent, mergeable sub-issues with clear scope and acceptance criteria. Use when user says 'split this issue', 'break this down', 'this issue is too big', 'splice this epic', 'create sub-issues', or 'decompose this task'. Do NOT use for planning implementation steps within a single issue (use plan-issue) or for creating a fresh issue from scratch.
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.
Create a GitHub issue with title and description. Use when the user wants to file a bug, request a feature, or create a tracking issue.
This skill is used when users mention "create issue", "register bug", "create task", "issue list", "my tasks", "assigned issues", "update issue", "change issue status", "search issues", "ticket", "issue", "bug report", etc. Provides Redmine issue management functionality.
Check GitHub Actions workflow runs from the past day, identify severe or consistent failures, and file an issue if actionable problems are found.
Create a plan collaboratively with the user, then convert the approved plan into a GitHub issue.