complete-github-issue

Assess and implement GitHub issue requirements using git history and linked pull requests.

5|1|Updated Oct 18, 2019

Search Tags:#automation #git #testing #code review #github #issue tracking

Ready to run

npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill complete-github-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: complete-github-issue
Source: https://github.com/Marshall-Hallenbeck/dot_files/tree/main/.claude/skills/complete-github-issue
Command: npx skills add https://github.com/Marshall-Hallenbeck/dot_files --skill complete-github-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents redundant work and ensures high-quality issue resolution by enforcing a rigorous reconnaissance phase before any code is written.

Core Features & Use Cases

Reconnaissance: Automatically checks git history, linked PRs, and codebase state to determine if an issue is already resolved.
Assessment: Provides a structured completion assessment to identify exactly which acceptance criteria remain unmet.
Verification: Mandates test coverage and validation before closing any issue, ensuring that implementation is robust and regression-free.

Quick Start

Use the complete-github-issue skill to assess and implement the requirements for issue number 42.

Frequently Asked Questions about complete-github-issue

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

FAQPage Schema

How do I systematically verify and resolve GitHub issues before writing new code?▼

To systematically verify and resolve GitHub issues, you must first perform reconnaissance by checking existing code, git history, and linked pull requests to determine if the issue is already resolved. This prevents redundant work before any code modification begins.

What is the best way to check if a GitHub issue has already been addressed in a linked pull request?▼

Checking if a GitHub issue is already addressed requires assessing linked pull requests and git history. This reconnaissance phase identifies exactly which acceptance criteria remain unmet, ensuring high-quality issue resolution without redundant development.

How do I enforce test coverage and validation when closing GitHub backlog issues?▼

Enforcing test coverage and validation when closing GitHub backlog issues requires a verification phase. You must mandate test coverage and validate acceptance criteria before closing any issue, ensuring that implementation is robust and regression-free.

Do I need the GitHub CLI to automate issue tracking and backlog management?▼

Yes, you need the GitHub CLI and standard git tooling to automate issue tracking and backlog management. These tools perform the necessary reconnaissance and verify acceptance criteria before any code modification occurs.

How do I assess unmet acceptance criteria for a bug resolution or feature implementation?▼

Assessing unmet acceptance criteria for bug resolution or feature implementation involves a structured completion assessment. This process evaluates the codebase state and linked PRs to identify exactly which requirements remain unmet before proceeding.

Why should I perform a reconnaissance phase before implementing a GitHub issue's requirements?▼

Performing a reconnaissance phase before implementing GitHub issue requirements prevents redundant work and ensures high-quality resolution. It enforces a rigorous check of git history and codebase state to verify the issue's current status prior to code modification.