issue-workflow-guardrail

Shape, orchestrate, implement, and close GitHub issues via a prepare/lint/finish workflow.

289|39|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/kxn/codex-remote-feishu --skill issue-workflow-guardrail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-workflow-guardrail
Source: https://github.com/kxn/codex-remote-feishu/tree/main/.codex/skills/issue-workflow-guardrail
Command: npx skills add https://github.com/kxn/codex-remote-feishu --skill issue-workflow-guardrail

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, and includes scripts (resource) components.

What problem does it solve?

Shape, orchestrate, implement, and close GitHub issues in this repository through a fixed prepare/lint/finish workflow.

Core Features & Use Cases

  • Shaping, splitting, and orchestrating issues from external reporters to internal execution units
  • Maintaining durable execution snapshots, staged plans, and verifier handoffs for safe, auditable progress
  • Enforcing fixed entry points (prepare, lint, finish) and guardrails to ensure correct close-out and minimal risk

Quick Start

To start, run the fixed issue workflow using issuectl.sh to prepare, lint, and finish an issue.

Frequently Asked Questions about issue-workflow-guardrail

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

FAQPage Schema
How do I orchestrate GitHub issues with structured workflow guardrails?

GitHub issue orchestration uses a fixed prepare, lint, and finish workflow to shape raw and external reporter issues into structured execution units. It maintains durable execution snapshots and staged plans to guide safe implementation and closure.

What is a prepare lint finish workflow for GitHub issue management?

A prepare lint finish workflow is a structured process for GitHub issue management that enforces guardrails through fixed CLI commands. It shapes issues, creates execution decision records, stages plans, and mandates verifier handoffs before meeting specific close-out criteria.

How do I split parent and child GitHub issues for execution?

Split parent and child GitHub issues by shaping external reporter issues into internal execution units using the prepare workflow stage. This creates durable execution snapshots that orchestrate implementation and guide the subsequent lint and finish stages.

Do I need Go to run issue workflow automation scripts?

Yes, you need Go installed because the issue workflow automation scripts depend on the Go environment to execute. The scripts enforce the fixed prepare, lint, and finish guardrails required for durable execution and issue closure.

How do execution decision records and verifier handoffs work for GitHub issues?

Execution decision records and verifier handoffs work as enforced guardrails within the issue workflow, capturing staged plans and mandating verification before closure. They ensure auditable progress and minimal risk by requiring specific close-out criteria via fixed CLI commands.