github-workflow

Coordinate GitHub repository changes through an issue-first, pull-request-based workflow.

Updated May 14, 2026
One-click install
npx skills add https://github.com/jinke5245/skills --skill github-workflow-jinke5245
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflow
Source: https://github.com/jinke5245/skills/tree/main/skills/github-workflow
Command: npx skills add https://github.com/jinke5245/skills --skill github-workflow-jinke5245

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of making repository changes in GitHub projects while keeping every change tracked, reviewed, and merge-ready.

Core Features & Use Cases

  • Issue-first planning: Create semantic issues before editing code so work stays scoped and easy to track.
  • Pull-request delivery: Use GitHub CLI to create issue-linked branches, focused commits, and draft pull requests.
  • Conservative repository hygiene: Reuse existing templates and labels, avoid label guessing, and follow repository conventions for reviews and updates.
  • Use Case: A maintainer asks for a documentation fix in a GitHub repo, and this Skill helps draft the issue, branch, commit, and PR workflow end to end.

Quick Start

Ask the assistant to help you make a GitHub repository change using the issue-first workflow and have it draft the issue and pull request plan.

Frequently Asked Questions about github-workflow

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

FAQPage Schema
How do I create a pull request from an issue using GitHub CLI?

To create a pull request from an issue using GitHub CLI, this Skill coordinates an issue-first workflow by drafting semantic issues, creating issue-prefixed branches, making focused commits, and opening draft pull requests.

What is an issue-first workflow for GitHub repository maintenance?

An issue-first workflow for GitHub repository maintenance creates semantic issues before editing code to keep work scoped and trackable, followed by issue-prefixed branches, semantic commits, and review-feedback handling for merge-ready pull requests.

Can I use my existing GitHub templates and labels for pull requests?

Yes, you can use existing GitHub templates and labels for pull requests. This Skill applies conservative repository hygiene by reusing available templates and avoiding label guessing to follow your repository conventions.

How do I handle review feedback on a GitHub pull request?

To handle review feedback on a GitHub pull request, this Skill manages review-feedback handling by updating issue-prefixed branches with semantic commits while maintaining repository conventions for reviews and updates.

What's the best way to track GitHub changes for documentation fixes?

The best way to track GitHub changes for documentation fixes is an issue-first, pull-request-based workflow that drafts the issue, creates linked branches, makes focused commits, and opens a draft pull request end to end.

Do I need GitHub CLI installed to automate pull request workflows?

Yes, you need GitHub CLI installed to automate this pull request workflow. The Skill uses GitHub CLI to create issue-linked branches, focused commits, and draft pull requests for your repository changes.