issue▌

Create GitHub issues from specification files using the feature_request.yml template. \n \n Analyzes specification files to extract requirements and automatically generates issue titles and descriptions \n Searches existing issues to prevent duplicates before creating new ones \n Supports both creating new issues and updating existing ones via the GitHub API \n Applies feature and enhancement labels automatically based on specification content \n

Resolve a GitHub issue from intake through fix, validation, and push using gh, local edits, XcodeBuildMCP, and git.

Intermittent issues are the most difficult to debug because they don't occur consistently. Systematic approach and comprehensive monitoring are essential.

Use this skill when the user wants to solve or continue a GitHub issue end-to-end, including short current-repo prompts like solve #123, direct GitHub issue URLs, or requests like lets work on https://github.com/owner/repo/issues/123.

Automated GitHub issue triage with real-time streaming analysis and background task parallelization. \n \n Launches one independent background task per issue for concurrent analysis, eliminating sequential bottlenecks \n Streams results in real-time as each task completes, providing immediate visibility into critical issues and recommended actions \n Categorizes issues by type (bug, feature, question, invalid) and status (resolved, needs action, can close, needs info) with priority flagging for

Investigate a reported problem, find its root cause, and create a GitHub issue with a TDD fix plan. This is a mostly hands-off workflow - minimize questions to the user.