skills.rest
ereferen
ereferenCOMMUNITY
Explore all skills by this author →
GitHub

issue

Automate GitHub issue workflows from retrieval to pull request creation.

Updated Jan 24, 2026
Search Tags:#automation#workflow#testing#github#issue#pr#branch-management
One-click install
npx skills add https://github.com/ereferen/zellij-toolbox --skill issue-ereferen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/ereferen/zellij-toolbox/tree/main/.claude/skills/issue
Command: npx skills add https://github.com/ereferen/zellij-toolbox --skill issue-ereferen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end GitHub issue workflow, transforming an issue into a branch, implementing changes, running tests, and opening a pull request with minimal manual steps.

Core Features & Use Cases

  • End-to-end workflow: fetch an issue by number, create a feature branch, implement changes, run tests, and prepare a PR.
  • Issue-centric planning: list open issues, view status of current work, and derive work from issue metadata.
  • Consistent contributor experience: generate conventional commit messages and ensure test suite compliance before PR creation.

Quick Start

Run /issue 123 to start working on issue number 123.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I automate a GitHub issue workflow from branch creation to pull request?▼

To automate a GitHub issue workflow, use a single command to fetch an issue, create a feature branch, implement changes, run tests, and open a pull request. This coordinates Git operations and issue metadata for end-to-end automation.

Can I list open GitHub issues and check the status of my current work?▼

You can list open GitHub issues and check work status using the /issue list and /issue status commands. These issue-centric planning commands retrieve issue metadata and track the progress of your current development workflow.

How do I ensure my automated pull requests pass test validation and use conventional commits?▼

Automated pull requests ensure test validation by running the test suite before PR creation and generating consistent conventional commit messages. This guarantees test compliance and creates auditable commits tied to the original issue.

What is the best way to start issue-driven development using a single command?▼

The best way to start issue-driven development is running the /issue <number> command. This triggers the end-to-end workflow to fetch the specified GitHub issue, derive work from its metadata, create a branch, and prepare a pull request.

Do I need any external dependencies to automate issue retrieval and PR creation?▼

No external dependencies are required to automate issue retrieval and PR creation. The workflow coordinates directly with Git operations, issue metadata, and PR workflows natively to transform issues into merged code.

Why should I use an automated issue workflow instead of manual branch management for GitHub issues?▼

An automated issue workflow eliminates manual branch management by transforming an issue into a branch, implementing changes, and opening a pull request with minimal steps. It ensures consistent contributor experiences and auditable commits.

Related Skills

Explore More Software Engineering Skills→
519lab519lab
2

github-auth

Configure HTTPS personal access tokens or SSH keys for GitHub authentication.

Official
Intermediate
taloncjonestaloncjones

ship

Automate code review, testing, version bump, merge, and post-merge cleanup for pull requests.

Community
Advanced
JaiminVadadoriyaJaiminVadadoriya
1

ai-qa-review

Detect test smells and analyze code testability in test suites.

Community
Advanced
toqoztoqoz

github-release-pr

Automate GitHub release pull requests between development and production branches.

Community
Advanced