github-issue-from-wip

Name: github-issue-from-wip
Availability: InStock
Author: Leigh

Generates a draft GitHub issue from the current branch's uncommitted changes.

1|Updated Jan 24, 2021

Search Tags:#automation #github #diff #issue #work-in-progress #wip

Ready to run

npx skills add https://github.com/leighmcculloch/dotfiles --skill github-issue-from-wip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-issue-from-wip
Source: https://github.com/leighmcculloch/dotfiles/tree/main/files/claude/skills/github-issue-create-from-wip
Command: npx skills add https://github.com/leighmcculloch/dotfiles --skill github-issue-from-wip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically converts ongoing work-in-progress on a feature branch into a well-formed GitHub issue by analyzing the differences against the determined base branch, ensuring traceability of completed and pending work.

Core Features & Use Cases

Context extraction: Determines the base branch (ancestor or default) and diffs the WIP changes to capture the scope of work.
Future-tense summarization: Produces a problem-focused description in the future tense that aligns with issue tracking practices.
Hand-off readiness: Produces structured inputs suitable for the github-issue skill to create the actual GitHub issue.

Quick Start

Run the WIP-to-issue workflow on your feature branch to generate a draft GitHub issue description ready for review.

Frequently Asked Questions about github-issue-from-wip

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

FAQPage Schema

How do I automatically create a GitHub issue from work-in-progress on a feature branch?▼

To create a GitHub issue from work-in-progress, this skill analyzes your feature branch changes against the base branch and synthesizes a problem-focused description. It generates structured inputs ready for issue creation to formalize pending work.

What is the best way to convert uncommitted feature branch changes into a tracked GitHub issue?▼

Converting feature branch changes into a tracked GitHub issue is done by computing the diff against the ancestor branch. The skill produces a future-tense problem statement that aligns with standard issue tracking practices for review.

Does generating an issue from a diff require manually specifying the base branch?▼

Generating an issue from a diff does not require manually specifying the base branch. The skill automatically determines the appropriate base, whether an ancestor or default branch, to accurately capture the scope of work.

How does the work-in-progress issue generator format the branch diff data?▼

The work-in-progress issue generator formats branch diff data by synthesizing a future-tense problem statement. It extracts context from the changes and prepares structured inputs suitable for the github-issue workflow to create the issue.

Can I use this to formalize a bug-fix in progress as a GitHub issue?▼

You can use this to formalize a bug-fix in progress as a GitHub issue. It applies whenever a feature or bug-fix is ongoing on a branch, inspecting the data to prepare a draft description for review.

When should I avoid using automated work-in-progress to issue conversion?▼

You should avoid using automated work-in-progress conversion when a formal issue already exists or when branch changes lack sufficient context. The skill requires meaningful diff data against the base branch to synthesize a problem statement.