implement-github-issue

Implement GitHub issues by reading issue text and executing file-level plans.

58|18|Updated May 22, 2020
One-click install
npx skills add https://github.com/gregrickaby/viewer-for-reddit --skill implement-github-issue-gregrickaby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-github-issue
Source: https://github.com/gregrickaby/viewer-for-reddit/tree/main/.agents/skills/implement-github-issue
Command: npx skills add https://github.com/gregrickaby/viewer-for-reddit --skill implement-github-issue-gregrickaby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams automate end-to-end GitHub issue handling by reading a pasted issue, evaluating constraints, and orchestrating a plan to implement and validate changes within a repository.

Core Features & Use Cases

  • Issue interpretation: Treats a GitHub issue as the authoritative spec for implementation.
  • Multi-file exploration: Analyzes all referenced source files and dependencies to inform planning.
  • Plan creation & execution: Generates a file-by-file implementation plan, resolves ambiguities with the user, executes steps, and validates results.
  • Interactive refinement: Prompts for clarifications on ambiguities before writing code.
  • Lifecycle alignment: Works from issue receipt to validated merge readiness.

Quick Start

Paste a GitHub issue URL or say "implement this issue" to start the end-to-end workflow.

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 start to finish?▼

Automating GitHub issue implementation involves reading the issue text as an authoritative spec, exploring referenced files, generating a plan, resolving ambiguities interactively, executing edits, and validating results for audit-ready reporting.

What is the best way to handle ambiguous requirements in a GitHub issue before writing code?▼

Handling ambiguous GitHub issue requirements requires interactive refinement, prompting the user for clarifications to resolve uncertainties before executing the file-by-file implementation plan and writing any code.

Can I use a pasted GitHub issue URL as the sole specification for code changes?▼

Yes, you can use a pasted GitHub issue URL as the authoritative specification for code changes by triggering an end-to-end workflow that analyzes dependencies and orchestrates file-level edits.

Does this GitHub issue workflow support multi-file exploration and dependency analysis?▼

Yes, the GitHub issue workflow supports multi-file exploration by analyzing all referenced source files and dependencies within a repository to inform the generation of a precise implementation plan.

How do I validate code changes against the original GitHub issue requirements?▼

Validating code changes against GitHub issue requirements is achieved through comprehensive validation during execution, ensuring the implementation satisfies the original spec and reaches a validated merge-ready state.