gh-workflow-manager

Manage GitHub issues, branches, and pull requests with automated workflows.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/SolaneHub/PokeMMO-Compendium --skill gh-workflow-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-workflow-manager
Source: https://github.com/SolaneHub/PokeMMO-Compendium/tree/main/.gemini/skills/gh-workflow-manager
Command: npx skills add https://github.com/SolaneHub/PokeMMO-Compendium --skill gh-workflow-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the entire development lifecycle from issue tracking to Pull Request creation, ensuring consistency and adherence to best practices.

Core Features & Use Cases

  • Issue Management: Lists and views GitHub issues to track tasks.
  • Branching: Creates feature branches directly from issue numbers.
  • Code Quality: Enforces import aliasing, linting, and validation before commits.
  • Pull Request Creation: Automates PR creation with proper titles, bodies, and labels.
  • Use Case: When starting a new feature, you can use this skill to automatically create a branch named issue-123-fix-login-bug, implement the fix, and then generate a Pull Request ready for review.

Quick Start

Use the gh-workflow-manager skill to create a branch for issue number 42 with the description add login form.

Frequently Asked Questions about gh-workflow-manager

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

FAQPage Schema
How do I automate GitHub issue tracking and branch creation from an issue number?

Automating GitHub issue tracking and branch creation involves listing issues and generating feature branches directly from issue numbers. This workflow ensures consistent branch naming and tracks tasks automatically before development begins.

What's the best way to create standardized pull requests with proper titles and labels?

Creating standardized pull requests requires automating PR generation with predefined titles, bodies, and labels. This ensures consistency across reviews and enforces development best practices without manual formatting effort.

How does linting and validation work before committing and pushing changes in a GitHub workflow?

Linting and validation before committing enforce code quality by checking import aliasing and formatting rules. This automated process runs validation checks to prevent invalid code from being pushed to the GitHub repository.

Can I generate a pull request automatically after fixing an issue branch?

Generating a pull request after fixing an issue branch is supported by automating the creation process. The system produces a PR with standardized titles, bodies, and labels ready for review once changes are committed.

Do I need any specific dependencies to manage GitHub workflows for branches and pull requests?

Managing GitHub workflows for branches and pull requests does not require specific dependencies. The skill operates independently to automate issue management, branching, and PR creation without external component installations.

When should I not use automated branching directly from GitHub issue numbers?

Automated branching from GitHub issue numbers may not suit projects lacking strict issue tracking workflows. If your development process does not rely on numbered issues or standardized pull request labels, this automation approach has limited value.