Skip to content

giuseppe-trisciuoglio/developer-kit / plugins/developer-kit-core/skills/github-issue-workflow

github-issue-workflow

Flagged

Provides a structured 8-phase workflow for resolving GitHub issues in Claude Code. Covers fetching issue details, analyzing requirements, implementing solutions, verifying correctness, performing code review, committing changes, and creating pull requests. Use when user asks to resolve, implement, work on, fix, or close a GitHub issue, or references an issue URL or number for implementation.

references/prerequisites.md

View on GitHub
# Prerequisites - Complete Reference

## Verification Commands

Before starting the GitHub Issue workflow, verify all required tools are available and properly configured.

### GitHub CLI

```bash
# Check if GitHub CLI is installed
gh --version

# Verify authentication (shows login status and scopes)
gh auth status

# If not authenticated, run:
gh auth login
# Follow prompts to authenticate with GitHub account
```

### Git Configuration

```bash
# Verify git is installed
git --version

# Check user name is configured
git config --get user.name
# If not set: git config --global user.name "Your Name"

# Check user email is configured
git config --get user.email
# If not set: git config --global user.email "your.email@example.com"

# Verify we're in a git repository
git rev-parse --git-dir

# Check git remote is configured
git remote -v
# Should show origin URL
```

### Repository Information

```bash
# Get repository owner and name
REPO_INFO=$(gh repo view --json owner,name -q '.owner.login + "/" + .name')
echo "Repository: $REPO_INFO"

# Get default branch
TARGET_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5)
TARGET_BRANCH=${TARGET_BRANCH:-main}
echo "Default branch: $TARGET_BRANCH"

# Check if gh can access this repository
gh repo view
```

## Setup Instructions

### Install GitHub CLI

**macOS:**
```bash
brew install gh
```

**Linux:**
```bash
# Ubuntu/Debian
sudo apt install gh

# Fedora
sudo dnf install gh

# Arch Linux
sudo pacman -S gh
```

**Windows:**
```bash
winget install --id GitHub.cli
```

### Authenticate GitHub CLI

```bash
gh auth login
# Follow interactive prompts:
# 1. Choose account (GitHub.com or GitHub Enterprise)
# 2. Choose protocol (HTTPS or SSH)
# 3. Authenticate with browser or device code
```

### Configure Git

```bash
# Set your name (appears in commits)
git config --global user.name "Your Name"

# Set your email (must match GitHub account)
git config --global user.email "your.email@example.com"

# Optionally set default branch name
git config --global init.defaultBranch main
```

## Troubleshooting

### gh: command not found
- Install GitHub CLI using your package manager
- On macOS: `brew install gh`

### gh auth status shows "not logged in"
- Run `gh auth login` to authenticate
- Ensure your token has necessary scopes (repo, workflow)

### git: user.name not set
- Run `git config --global user.name "Your Name"`
- Run `git config --global user.email "your.email@example.com"`

### git remote not configured
- Ensure you're in a git repository: `git init` if needed
- Add remote: `git remote add origin <repository-url>`
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 467kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall