github-issue-workflow

Automate issue-first GitHub workflows from branch creation through PR merge.

2|1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/robinmordasiewicz/terraform-provider-f5xc --skill github-issue-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-workflow
Source: https://github.com/robinmordasiewicz/terraform-provider-f5xc/tree/main/.claude/skills/github-issue-workflow
Command: npx skills add https://github.com/robinmordasiewicz/terraform-provider-f5xc --skill github-issue-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issue-first GitHub development workflows help engineering teams ensure work starts from a tracked issue and follows a disciplined lifecycle, reducing misalignment and rework.

Core Features & Use Cases

  • Issue-first governance: require a GitHub issue as the origin for all work and link branches to that issue.
  • Branching discipline: automatically correlate feature branches with issue numbers and maintain traceability.
  • Validation-driven delivery: enforce a cycle of implementation, testing, review, and verified merge before closure.
  • Lifecycle cleanup: ensure issues, branches, and PRs are closed or archived after merge.

Quick Start

Identify or create a GitHub issue, then follow the workflow to create a linked feature branch, implement changes, validate, and open a PR.

Frequently Asked Questions about github-issue-workflow

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

FAQPage Schema
How do I enforce an issue-first GitHub workflow for my development process?

Issue-first GitHub workflow automation requires a tracked issue as the origin for all work, linking feature branches to issue numbers to maintain traceability and reduce misalignment. This enforces disciplined lifecycle management from issue creation through merge and cleanup.

How do I link a GitHub feature branch to an issue automatically?

Linking a GitHub feature branch to an issue requires correlating the branch name with the issue number and referencing the issue in commits. This maintains traceability throughout the development lifecycle until the issue is closed via PR merge.

What is the best way to manage GitHub issue lifecycle cleanup after a pull request?

GitHub issue lifecycle cleanup requires closing or archiving the issue, branch, and PR after merge. This ensures the repository remains organized and completes the validation-driven delivery cycle.

How do I automate a validation loop with testing and linting before a GitHub PR?

Automating a validation loop before a GitHub PR requires enforcing a cycle of implementation, testing, linting, and review. This validation-driven delivery verifies changes before managing merge and cleanup through the PR workflow.

Does this GitHub issue workflow require any specific dependencies or components?

No, this GitHub issue workflow does not require specific dependencies or components. It applies to any GitHub repository task, feature, or bug fix that starts from a tracked issue and follows a disciplined lifecycle.