Loading...
Loading...
Found 17 Skills
File a GitHub issue for local integration test failures. TRIGGERS: file test bug, report test failure, create bug for test, integration test failed, test failure issue, junit failure
Configure a Stop hook that surfaces unfinished todos before a session ends and suggests creating GitHub issues for deferred work. Use when you want unfinished Claude Code session tasks automatically flagged for GitHub issue creation at session end.
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.
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.
Generates detailed, architect-quality GitHub issues from short instructions. Analyzes the project's actual stack, architecture, and codebase before writing. Detects duplicate issues with intelligent multi-strategy search, validates and creates labels, enforces title conventions, controls scope, and publishes via `gh` CLI with robust error handling. Use this skill whenever the user wants to create a GitHub issue, report a bug, propose a feature, request a refactor, or file any kind of technical issue — even if they just say something brief like "we need to fix the auth flow" or "create an issue for X". Also triggers on: "open an issue", "file a bug", "I want to propose...", "add this to the backlog", "gh issue", or any request that implies creating a trackable work item on GitHub.