executing-development-issues

Automate GitHub issue lifecycle from branching to merging with quality gates.

1|Updated Oct 21, 2025

Search Tags:#workflow automation #GitHub #issue management #quality gates #local issues #check-all

Ready to run

npx skills add https://github.com/bryonjacob/aug --skill executing-development-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-development-issues
Source: https://github.com/bryonjacob/aug/tree/main/aug-dev/skills/executing-development-issues
Command: npx skills add https://github.com/bryonjacob/aug --skill executing-development-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end lifecycle of issues from branching to merging.

Core Features & Use Cases

End-to-end lifecycle management for GitHub issues and local ISSUES.LOCAL workflows.
Guided branching, implementation, testing, PR creation, and merge with integrated quality gates.
TDD-driven workflow ensuring one issue is completed before starting the next.

Quick Start

gh issue view [NUMBER] # GitHub cat ISSUES.LOCAL/LOCAL###-Title.md # Local git checkout -b [ISSUE_ID]-description just test-watch just check-all gh pr create --draft gh pr ready gh pr merge --squash --delete-branch

Frequently Asked Questions about executing-development-issues

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

FAQPage Schema

How do I automate the GitHub issue lifecycle from branching to merging?▼

Automating the GitHub issue lifecycle involves guided branching, TDD implementation, running check-all quality gates, drafting PRs, and merging with strict release gates. This ensures one issue is fully resolved before starting the next.

What is the ISSUES.LOCAL workflow for issue management?▼

The ISSUES.LOCAL workflow is a local issue management process using markdown files (ISSUES.LOCAL/LOCAL###-Title.md) to track issues. It supports the same end-to-end lifecycle as GitHub issues, including branching, testing, and merging.

How do I enforce quality gates before creating a pull request?▼

To enforce quality gates before creating a pull request, run the check-all command after implementing changes with TDD. This ensures all tests and quality checks pass before drafting your PR for review.

Can I use test-driven development with GitHub issue automation?▼

Yes, TDD-driven workflow is integrated into GitHub issue automation. It guides you to implement with test-driven development, run quality gates via check-all, and ensure one issue is completed before starting the next.

Does this issue management workflow support both GitHub and local issues?▼

Yes, this issue management workflow supports both GitHub issues and local ISSUES.LOCAL workflows. It applies end-to-end lifecycle management including branching, testing, PR creation, and merging to both formats.

What are the limitations of automating issue lifecycle management?▼

The issue lifecycle automation enforces strict release gates and TDD, requiring all quality gates (check-all) to pass before merging. It focuses on one issue at a time, which may limit parallel workflow flexibility.