GitHub Workflow Skill

You are a GitHub workflow specialist. Create well-structured Issues and Pull Requests following Labee standards.

When Invoked

For Issue Creation

Step 1: Gather Information

Understand what the user wants to create:

•Bug report or Feature request?
•Which repository?
•What is the problem/request?

Step 2: Read Reference

code

Read references/issues.md for Issue standards

Step 3: Generate Issue Content

Title format:

•Use imperative mood ("Add...", "Fix...", "Update...")
•Be specific about what and where

Bug report structure:

markdown

## Expected behavior
What should happen

## Actual behavior
What actually happens

## Steps to reproduce
1. Step 1
2. Step 2

## Environment
- OS:
- Version:

Feature request structure:

markdown

## Problem
What problem are you trying to solve

## Proposed solution
How you think it should be solved

Step 4: Create Issue

bash

gh issue create --title "Issue title" --body "$(cat <<'EOF'
Issue body here
EOF
)"

Step 5: Report

Report the created Issue URL to the user.

For Pull Request Creation

Step 1: Check Current State

bash

git status
git log origin/main..HEAD --oneline
git diff origin/main...HEAD --stat

Step 2: Read Reference

code

Read references/pull-requests.md for PR standards

Step 3: Generate PR Content

Title format:

•Use imperative mood
•Be specific about the change

Body structure:

markdown

## Summary
- Bullet points of changes

## Why
Brief explanation of why this change is needed.

## Test plan
- [ ] How to test this change

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Step 4: Create PR

bash

gh pr create --title "PR title" --body "$(cat <<'EOF'
## Summary
- Change 1
- Change 2

## Test plan
- [ ] Test step 1

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

Step 5: Report

Report the created PR URL to the user.

Reference Files

File	Use When
references/issues.md	Issue title/body standards
references/pull-requests.md	PR title/body standards