issue

Automate GitHub issue classification, branch creation, and pull request setup.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/albertoirurueta/ai-catalog --skill issue-albertoirurueta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/albertoirurueta/ai-catalog/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/albertoirurueta/ai-catalog --skill issue-albertoirurueta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The 'issue' skill addresses the fragmented workflow of managing GitHub issues from creation to pull request setup, automating ticket classification, branch creation, and PR setup.

Core Features & Use Cases

  • Ticket Classification: Automatically classifies tickets as features or hotfixes.
  • Branch Creation: Creates a new branch with the appropriate prefix based on the ticket type.
  • PR Setup: Automatically pushes the branch and opens a pull request with basic description and review.
  • Use Case: If you have a ticket to be implemented and you want to automate the entire process of issue management, classification, branch creation, and PR setup in one go.

Quick Start

To start the issue management process for a GitHub issue with ID #42, use the command: /issue #42

Frequently Asked Questions about issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue management from ticket classification to pull request setup?

You can automate GitHub issue management end-to-end by classifying tickets as features or hotfixes, creating branches with appropriate prefixes, and pushing branches to automatically open pull requests with basic descriptions. This workflow requires GitHub API access to function.

Can I use this workflow to manage both GitHub and Jira tickets?

Yes, the workflow handles both GitHub and Jira tickets for issue classification and branch creation. However, the automated pull request closing behavior is specific to GitHub tickets, meaning Jira tickets will not trigger GitHub-specific PR closing actions.

How does ticket classification work when automating branch creation for pull requests?

Ticket classification automatically categorizes issues as either features or hotfixes. Based on this classification, the system creates a new branch with the appropriate prefix matching the ticket type, ensuring consistent branch naming conventions before pushing and opening a pull request.

Do I need GitHub API access to automate issue management and PR setup?

Yes, GitHub API access is required to automate the full issue lifecycle from ticket classification to PR setup. The automation uses Claude Code's skill invocation system to interact with GitHub repositories, create branches, and open pull requests programmatically.

What's the best way to start automating issue management for a specific GitHub issue?

To start automating issue management for a GitHub issue, use the command syntax with the issue ID, such as `/issue #42`. This triggers the full workflow: ticket classification, branch creation with appropriate prefixes, and automatic pull request setup with basic description and review.

What are the limitations of automating GitHub issue to pull request workflows?

The main limitation is that GitHub-specific PR closing behavior does not apply to Jira tickets, meaning cross-platform ticket handling has partial coverage. Additionally, the PR setup generates only basic descriptions and reviews, so further manual refinement of pull request details may still be required.