github-workflow

Manage GitHub issues, pull requests, and lifecycle transitions through a packaged gh-workflow tool.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/L3DigitalNet/project-standards --skill github-workflow-l3digitalnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-workflow
Source: https://github.com/L3DigitalNet/project-standards/tree/main/.agents/skills/github-workflow
Command: npx skills add https://github.com/L3DigitalNet/project-standards --skill github-workflow-l3digitalnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It enforces a consistent, auditable discipline for GitHub work state — typed issues, pinned fields, PR admission classes, and lifecycle synchronization — so agents and humans apply the same rules instead of improvising raw gh calls that skip validation. ## Core Features & Use Cases - Typed issue and field management: Create issues from a five-type vocabulary (Bug, Feature, Task, Initiative, Research) and set organization fields validated against a machine-readable org-schema.yaml baseline. - PR admission and lifecycle gating: Route every change through T0, handoff, release, or pull-request admission classes, with ready/merge/land commands that enforce structural, ready, and merge gates and synchronize the governing issue's Workflow field. - Audits, receipts, and summaries: Run read-only organization schema audits, per-item receipts, and operator summaries with typed findings and stable finding codes. - Use Case: When triaging a backlog, an agent loads this skill to classify issues, set Workflow and Priority fields via validated commands, and relay a verbatim operator summary of blocked and undefined work. ## Quick Start Ask the agent to triage the repository's open issues and present an operator summary using the github-workflow skill.

Frequently Asked Questions about github-workflow

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

FAQPage Schema
How do I create a typed GitHub issue with gh-workflow?▼

Run gh-workflow new with --type, --title, an optional --body-file, and --field flags. The tool scaffolds canonical body headings and validates field values against the org schema, refusing invalid values by naming the valid set.

How does the pull request admission system work?▼

Every commit on a governed branch is admitted by exactly one of four classes: T0, pull request, handoff, or release, each carrying a Workflow-Admission trailer. Everything else begins as a draft PR declaring Final, Supporting, or Standalone under a Governing work heading.

When should I load this skill instead of using raw gh commands?▼

Load it for triage, organization schema audits, T0 or relationship judgments, and uncommon recovery like partial mutations. Ordinary mutations and summaries are routed by the managed AGENTS.md block, and plain read-only queries are exempt.

Can agents modify GitHub organization schema or Issue Types?▼

No. Issue Types and Issue Fields are applied by humans only. Agents run gh-workflow audit to compare live state against the org-schema.yaml baseline read-only and report drift, never creating, renaming, or retiring schema elements.

What happens when a merge or ready command partially fails?▼

Paired commands are idempotent and resumable, so rerun them as-is. Synchronization is complete only after a clean run, and the JSON envelope's step statuses show exactly how far an interrupted command progressed.

What are the limitations of the gh-workflow tool?▼

The binary supports linux/amd64 only and runs under the operator's gh authentication with no packaged credentials. It contributes no CI workflow, so repositories must wire admission checks into their own CI for enforcement coverage.