workflow-scripts

Execute workflow helper scripts with JSON output and non-zero exit codes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ai212983/gh-csi --skill workflow-scripts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-scripts
Source: https://github.com/ai212983/gh-csi/tree/main/skills/workflow-scripts
Command: npx skills add https://github.com/ai212983/gh-csi --skill workflow-scripts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @gh-csi/workflow, and includes scripts (resource) components.

What problem does it solve?

Provides a stable, deterministic way to run lightweight workflow helper scripts locally so agents and CLI tools can perform GitHub-centric tasks without relying on ad-hoc runtime behavior.

Core Features & Use Cases

  • Thin wrapper scripts that delegate workflow logic to gh-csi workflow command modules for consistent behavior.
  • Deterministic execution contracts: scripts are expected to support --json output, exit non-zero on actionable failures, and keep stable CLI contracts.
  • Use Cases: create or reuse planning issues, read issue context, start branch work from an issue, hand off PRs for agent runs, request reviews, audit task completion, and resolve task links.

Quick Start

Run the create-or-reuse-plan-issue script to create or reuse a planning issue for the current repository.

Frequently Asked Questions about workflow-scripts

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

FAQPage Schema
How do I run deterministic local scripts for GitHub workflow automation?

Deterministic local scripts for GitHub workflow automation run as thin wrappers that delegate logic to gh-csi workflow modules, ensuring stable CLI contracts with JSON output and non-zero exit codes on failures for agent execution.

What GitHub workflow tasks can I automate using CLI scripts?

CLI scripts automate GitHub workflow tasks including creating planning issues, reading issue context, starting branch work from issues, handing off PRs for agent runs, requesting reviews, auditing task completion, and resolving task links.

Can I use these workflow scripts with agent tools that require JSON output?

These workflow scripts support agent tools requiring JSON output by providing deterministic execution contracts. They are designed to support --json output, exit non-zero on actionable failures, and maintain stable CLI contracts for reliable agent integration.

Do I need the gh-csi workflow module to run these GitHub workflow scripts?

The gh-csi workflow module is required to run these GitHub workflow scripts because they act as thin wrappers that delegate workflow logic to gh-csi workflow command modules for consistent behavior during local execution.

What's the best way to create a planning issue for GitHub development workflows?

Creating a planning issue for GitHub development workflows is handled by the create-or-reuse-plan-issue script, which creates or reuses a planning issue for the current repository as part of a deterministic local execution pipeline.

Why do my GitHub workflow scripts fail with non-zero exit codes during agent runs?

GitHub workflow scripts exit with non-zero codes on actionable failures by design, ensuring deterministic execution contracts. This behavior alerts agents and CLI tools to workflow errors during planning, PR handoff, branch creation, or review automation tasks.