github-issue-lifecycle-operations

Class-level GitHub issue lifecycle operations: issue creation, planning/execution routing, labels, evidence fields, roadmap anchors, closeout races, and visual planning.

5 stars

Best use case

github-issue-lifecycle-operations is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Class-level GitHub issue lifecycle operations: issue creation, planning/execution routing, labels, evidence fields, roadmap anchors, closeout races, and visual planning.

Teams using github-issue-lifecycle-operations should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/github-issue-lifecycle-operations/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/github/github-issue-lifecycle-operations/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/github-issue-lifecycle-operations/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How github-issue-lifecycle-operations Compares

Feature / Agentgithub-issue-lifecycle-operationsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Class-level GitHub issue lifecycle operations: issue creation, planning/execution routing, labels, evidence fields, roadmap anchors, closeout races, and visual planning.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Github Issue Lifecycle Operations

## When to Use
Use for GitHub issue intake, decomposition, planning, execution handoff, label/evidence automation, roadmap reuse, closeout, or cross-issue waves.

## Class-Level Workflow
1. Discover repo, existing anchors, labels, and issue state before writing.
2. Prefer durable umbrella/roadmap anchors over duplicate replacement epics.
3. Put command-heavy bodies in files to avoid shell quoting and command substitution hazards.
4. Maintain explicit evidence fields and closeout comments before state transitions.
5. Use checklist skills as support material, not separate discovery targets.

## Consolidated Session Learnings

The `references/` directory contains archived narrow skills absorbed during the 2026-04-29 umbrella consolidation pass. Use the subsections below as the class-level index, then open the named reference when a case-specific recipe is needed.
## Absorbed Narrow Skills (2026-04-29)

### `gh-issue-creation-full-repo-and-batch-setup`

- Former skill demoted to `references/gh-issue-creation-full-repo-and-batch-setup.md`.
- Preserved insight: Create multiple related GitHub issues safely by resolving full OWNER/REPO, checking duplicates and labels first, and verifying each created issue.

### `gh-work-execution`

- Former skill demoted to `references/gh-work-execution.md`.
- Preserved insight: Canonical GitHub issue execution route after plan approval — strengthened resource intelligence, TDD-first implementation, targeted validation, adversarial review, delegation controls for Codex agent teams, GitHub progress posting, future-issue capture, and commit/push with closeout discipline.

### `gh-work-execution-checklist`

- Former skill demoted to `references/gh-work-execution-checklist.md`.
- Preserved insight: Compact live-execution checklist companion for approved GitHub issue work. Use during active implementation as a fast operational route; gh-work-execution remains the canonical source of truth.

### `gh-work-planning`

- Former skill demoted to `references/gh-work-planning.md`.
- Preserved insight: Canonical GitHub issue planning route — issue intake, strengthened resource intelligence, repo-tracked plan artifact, adversarial review, GitHub progress posting, future-issue capture, explicit approval gate before execution, and execution-ready delegation packaging for Codex agent teams.

### `gh-work-planning-checklist`

- Former skill demoted to `references/gh-work-planning-checklist.md`.
- Preserved insight: Compact live-execution checklist companion for the canonical gh-work-planning route. Use for fast operational tracking during issue planning without replacing the full route.

### `github-comment-body-file-safety`

- Former skill demoted to `references/github-comment-body-file-safety.md`.
- Preserved insight: Prevent shell-quoting and command-substitution bugs when posting GitHub issue/PR comments or editing bodies with gh CLI.

### `github-interaction-limits-hardening`

- Former skill demoted to `references/github-interaction-limits-hardening.md`.
- Preserved insight: Lock down public GitHub repositories so only collaborators can interact with issues, PRs, comments, discussions, and other user-generated surfaces using repository interaction limits; includes expiry verification and renewal handling.

### `github-issue-automation-evidence-fields`

- Former skill demoted to `references/github-issue-automation-evidence-fields.md`.
- Preserved insight: Use when building GitHub issue classifiers, dashboards, closeout verifiers, or queue/report automation that depends on comments, approval evidence, or linked PR handoff state.

### `github-issue-closeout-race-safe`

- Former skill demoted to `references/github-issue-closeout-race-safe.md`.
- Preserved insight: Close GitHub issues without losing the evidence comment when multiple agents or races may close the issue concurrently.

### `github-issue-label-audit-and-command-bundles`

- Former skill demoted to `references/github-issue-label-audit-and-command-bundles.md`.
- Preserved insight: Safely turn drafted issue bodies into reusable gh issue create commands by auditing repo labels, exact duplicates, and auth first.

### `github-issue-label-existence-audit`

- Former skill demoted to `references/github-issue-label-existence-audit.md`.
- Preserved insight: Prevent GitHub issue creation failures by auditing exact label existence, duplicate titles, and partial-create risk before calling gh issue create.

### `github-roadmap-anchor-reuse`

- Former skill demoted to `references/github-roadmap-anchor-reuse.md`.
- Preserved insight: Reuse and reopen existing roadmap/epic GitHub issues instead of fragmenting work across duplicate replacement epics; retarget children and link active issues for continuity.

### `github-visual-planning-issues`

- Former skill demoted to `references/github-visual-planning-issues.md`.
- Preserved insight: Create review-friendly GitHub planning issues that supersede stale/seasonal issues and include source-backed image thumbnails for faster human review.

### `issue-tree-decomposition`

- Former skill demoted to `references/issue-tree-decomposition.md`.
- Preserved insight: Break a large umbrella GitHub issue into a layered tree of focused follow-on issues using read-only subagent analysis, then create the issues locally and update docs/parent issue with the issue map.

### `roadmap-anchor-issue-governance`

- Former skill demoted to `references/roadmap-anchor-issue-governance.md`.
- Preserved insight: Reopen and reuse the original roadmap/umbrella issue as the governance anchor; create new issues only for genuinely missing scoped work, then retarget/link all execution issues back to the anchor.

### `roadmap-issue-reopen-retarget-balance`

- Former skill demoted to `references/roadmap-issue-reopen-retarget-balance.md`.
- Preserved insight: Reopen existing roadmap anchors, close replacement epics, retarget new child issues, and add sequencing/de-dup comments so GitHub roadmap work preserves continuity and execution quality.

### `roadmap-to-github-issue-wave`

- Former skill demoted to `references/roadmap-to-github-issue-wave.md`.
- Preserved insight: Turn a roadmap/readiness review into a de-duplicated GitHub epic + child issue set with verification and explicit scope boundaries.

### `closed-issue-plan-refile-loop`

- Former skill demoted to `references/closed-issue-plan-refile-loop.md`.
- Preserved insight: Reopen and re-drive a previously closed GitHub plan issue after review/governance blockers are fixed, without prematurely restoring approval state.

### `preserved-plan-refile-with-attested-review-wave`

- Former skill demoted to `references/preserved-plan-refile-with-attested-review-wave.md`.
- Preserved insight: Reopen a previously closed GitHub issue with a preserved local plan, rewrite it into a conservative draft, and drive iterative attested adversarial review waves until it is truly approval-ready.

### `single-terminal-gh-issue-prompts`

- Former skill demoted to `references/single-terminal-gh-issue-prompts.md`.
- Preserved insight: Generate live issue-specific Codex prompts for a single terminal, with repo-aware path contracts and plan-gate safety checks.

### `plan-resubmit-wave-prompts`

- Former skill demoted to `references/plan-resubmit-wave-prompts.md`.
- Preserved insight: Run a planning-only multi-terminal wave to harden blocked `status:plan-review` issues for fresh adversarial re-review, with zero implementation work and explicit path ownership.

### `parallel-plan-drafting-worktrees`

- Former skill demoted to `references/parallel-plan-drafting-worktrees.md`.
- Preserved insight: Draft multiple follow-up GitHub issue plans in parallel using isolated git worktrees plus background Codex print-mode runs, while keeping governance-safe boundaries and avoiding shared-file contention.

### `parallel-approved-issue-worktrees`

- Former skill demoted to `references/parallel-approved-issue-worktrees.md`.
- Preserved insight: Launch approved GitHub issue implementation in parallel using isolated git worktrees, committed execution-pack prompts, local plan-approved markers, and direct background Codex runs when delegate_task workers are unreliable for real repo writes.

### `plan-gated-issue-execution-wave`

- Former skill demoted to `references/plan-gated-issue-execution-wave.md`.
- Preserved insight: Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.

### `continuous-planning-pipeline`

- Former skill demoted to `references/continuous-planning-pipeline.md`.
- Preserved insight: Maintain a standing day/night GitHub issue pipeline so agents always have planned, reviewed, user-approved work for overnight execution and next-day QA/approval.

### `plan-automation-contracts`

- Former skill demoted to `references/plan-automation-contracts.md`.
- Preserved insight: Tighten plans for scheduled/reporting workflows and multi-source detectors so adversarial review can verify runtime, publication, and normalization behavior.

### `next-wave-handoff-bundle`

- Former skill demoted to `references/next-wave-handoff-bundle.md`.
- Preserved insight: Build a docs-only execution handoff bundle after a completed implementation wave — follow-up issue drafts, scoped authorization note, deploy checklist, operator note, copy/paste command bundle, and incremental commit hygiene.

Related Skills

memory-bridge-operations

5
from vamseeachanta/workspace-hub

Operate and recover the Hermes-to-repo memory bridge: drift checks, quality gate, bridge commits, push verification, and stash recovery when pre-bridge scripts fail after generating outputs.

plan-gated-issue-execution-wave

5
from vamseeachanta/workspace-hub

Execute a multi-issue architecture/planning wave in a plan-gated repo, then safely transition approved issues into implementation with file-based Codex prompts, local approval markers, subprocess monitoring, and cleanup handling for sandbox/hook edge cases.

tax-filing-session-setup-with-github-tracking

5
from vamseeachanta/workspace-hub

Structured workflow for preparing and tracking a tax filing session using prepared documents, task checklist, and GitHub issue cross-referencing

tax-filing-session-setup-with-github-traceability

5
from vamseeachanta/workspace-hub

Structured workflow for setting up a multi-file tax filing session with GitHub issue tracking and prepared-file validation

staged-issue-tree-creation-with-deduplication

5
from vamseeachanta/workspace-hub

Pattern for creating hierarchical GitHub issue trees from phased project plans while checking for duplicate/overlapping issues

plan-gated-issue-validation-workflow

5
from vamseeachanta/workspace-hub

Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables

plan-gated-issue-implementation

5
from vamseeachanta/workspace-hub

Workflow for executing pre-approved GitHub issues with mandatory validation checkpoints

github-issue-structure-for-personal-finance-tracking

5
from vamseeachanta/workspace-hub

Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)

plan-draft-review-artifact-truthfulness-and-issue-body-alignment

5
from vamseeachanta/workspace-hub

Keep plan drafts truthful during adversarial review loops by verifying real provider artifact state on disk and aligning the GitHub issue body to the bounded plan tranche before claiming approval-readiness.

parallel-llm-wiki-gap-to-issues

5
from vamseeachanta/workspace-hub

Use parallel subagents to mine remaining LLM-wiki/document-intelligence gaps, de-duplicate against existing GitHub issues, then create only the strongest bounded follow-on issues.

llm-wiki-ecosystem-gap-to-issues

5
from vamseeachanta/workspace-hub

Review the workspace-hub LLM-wiki/document-intelligence ecosystem, identify high-leverage gaps, and create grounded GitHub feature issues without duplicating existing work.

interactive-issue-execution-worktree-guardrails

5
from vamseeachanta/workspace-hub

Execute approved GitHub issues in isolated worktrees with interactive Codex/Codex runs, while containing agent drift and salvaging progress when provider/runtime problems occur.