skills.rest
poindexter12
poindexter12COMMUNITY
Explore all skills by this author →
GitHub

gh-issue-lifecycle

Automate GitHub issue lifecycle state transitions and PR linking.

7|Updated Nov 23, 2025
Search Tags:#automation#workflow#github#issue#triage#pull-request#branch-naming
One-click install
npx skills add https://github.com/poindexter12/waypoint --skill gh-issue-lifecycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-issue-lifecycle
Source: https://github.com/poindexter12/waypoint/tree/main/workflows/skills/gh-issue-lifecycle
Command: npx skills add https://github.com/poindexter12/waypoint --skill gh-issue-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates GitHub issue lifecycle management by codifying a repeatable state machine and code integration patterns.

Core Features & Use Cases

  • State transitions from needs-triage to accepted, in-progress, and completed, including blocked and needs-info branches.
  • Branch naming and PR linkage conventions to ensure traceability (e.g., feat/123-description; Closes #123).
  • Bulk operations and manual close reasoning to manage large issue sets efficiently.

Quick Start

Create a new issue, triage it, start work with a feature branch like feat/123-description, and link the PR to close the issue.

Frequently Asked Questions about gh-issue-lifecycle

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

FAQPage Schema
How do I automate GitHub issue triage and tracking from start to completion?▼

Automate GitHub issue triage by codifying a repeatable state machine that transitions issues from needs-triage through accepted, in-progress, and completed, including blocked and needs-info branches for efficient governance.

What naming conventions should I use for GitHub branches and pull requests?▼

Use branch naming conventions like feat/123-desc and PR titles with Closes references to ensure traceability. This links pull requests directly to GitHub issues for automated closure upon merge.

Can I perform bulk operations on GitHub issues to manage large backlogs?▼

Yes, you can execute bulk close and relate workflows alongside manual close reasoning to manage large GitHub issue sets efficiently across software projects using issues to drive development.

What is the best way to link pull requests to GitHub issues automatically?▼

The best way to link pull requests to GitHub issues is by imposing branch naming conventions like feat/123-description and using PR titles with Closes #123 references to enforce traceability.

Does this GitHub issue lifecycle workflow require any external dependencies?▼

No, this GitHub issue lifecycle workflow does not require external dependencies. It applies code integration patterns and state transitions directly to issue triage, backlog planning, and work-in-progress tracking.

When should I use manual close reasoning instead of automated PR linking?▼

Use manual close reasoning for GitHub issues when bulk operations are needed for large sets or when work-in-progress tracking requires explicit governance rather than automatic PR closure references.

Related Skills

Explore More Software Engineering Skills→
dformosodformoso

github-triage

Automate GitHub issue triage using labels and a predefined state machine.

Community
Intermediate
richardnpaulrichardnpaul

project-flow-ops

Coordinates GitHub issues/PRs and Linear tasks into a unified execution flow for triage and classification.

Community
Intermediate
hivellmhivellm
15

rulebook-git-workflow

Enforce branch naming, conventional commits, and PR guidelines in Git workflows.

Official
Basic
nbramianbramia
20

pr-check

Validate PR branch naming, titles, descriptions, and sizing against project standards.

Community
Advanced