implement-github-issue

Automate GitHub issue workflows from reading issues to opening pull requests.

2|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/brandonavant/harness-engineering-guide --skill implement-github-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-github-issue
Source: https://github.com/brandonavant/harness-engineering-guide/tree/main/.claude/skills/implement-github-issue
Command: npx skills add https://github.com/brandonavant/harness-engineering-guide --skill implement-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Implementing issues on GitHub can be time-consuming and error-prone; this workflow automates the full lifecycle from reading the issue to opening a PR.

## Core Features & Use Cases

  • Read issue details via gh to gather number, title, body, and labels.
  • Create and switch to a branch using a naming convention derived from issue labels or title keywords.
  • Apply changes following the issue body with minimal steps and consistent style.
  • Commit, push, and open a PR with a standardized message and description.

### Quick Start Ask Claude to implement issue #42 by reading the issue, creating a branch, applying changes, and opening a PR.

Frequently Asked Questions about implement-github-issue

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

FAQPage Schema
How do I automate GitHub issue implementation from reading details to opening a pull request?

Automate GitHub issue implementation by reading issue details via gh, creating a feature branch, committing changes with references, and generating a PR description with a link automatically.

How does branch naming work when automating GitHub issue workflows?

Branch naming in GitHub issue workflows derives its convention from the issue labels or title keywords, ensuring the feature branch name aligns with the issue context before pushing.

Can I use this workflow to read GitHub issue details like body and labels before creating a branch?

Yes, reading GitHub issue details via gh gathers the number, title, body, and labels to inform branch naming and ensure changes follow the issue body accurately.

What's the best way to ensure a clean working tree before creating a feature branch for a GitHub issue?

To ensure a clean working tree before creating a feature branch, the GitHub issue workflow verifies the repository state first, preventing uncommitted changes from interfering with the new branch.

Do I need the gh CLI installed to automate pull request creation from GitHub issues?

Yes, the gh CLI is required to read GitHub issue details, push the feature branch, and generate the pull request description and link during the automated workflow.

Does this GitHub issue automation work for issues that require actual implementation work?

Yes, this GitHub issue automation applies specifically to issues requiring implementation work, handling the end-to-end lifecycle from reading the issue to opening a pull request.