issue-to-setup-yaml

Parse a GitHub issue and generate a setup.yaml skeleton.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/NagasakaH/dev-process --skill issue-to-setup-yaml
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-to-setup-yaml
Source: https://github.com/NagasakaH/dev-process/tree/main/.claude/skills/development/issue-to-setup-yaml
Command: npx skills add https://github.com/NagasakaH/dev-process --skill issue-to-setup-yaml

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issueからsetup.yamlを自動生成するこのスキルは、手作業でのドキュメント作成を削減します。Issueの情報を抽出して、開発タスクのSSOTを提供する setup.yaml の雛形を作成します。

Core Features & Use Cases

  • GitHub issue から ticket_id と task_name を抽出し、階層化された description を構築します。
  • issue URL 形式または owner/repo/issue_number の入力で setup.yaml を生成します。
  • 出力ファイルは setup-{ticket_id}.yaml の形式で保存され、開発計画・実装のワークフローを加速します。

Quick Start

Provide the AI with an issue URL like https://github.com/org/repo/issues/123 to generate a setup.yaml skeleton.

Frequently Asked Questions about issue-to-setup-yaml

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

FAQPage Schema
How do I generate a setup.yaml file from a GitHub issue?

To generate a setup.yaml from a GitHub issue, provide the AI with an issue URL like https://github.com/org/repo/issues/123. The Skill parses the issue and outputs a hierarchical setup.yaml skeleton.

What is a setup.yaml file used for in development planning?

A setup.yaml file provides a single source of truth for development tasks by structuring ticket_id, task_name, and description hierarchically. It acts as a skeleton to accelerate development planning and implementation workflows.

Can I use issue numbers instead of URLs to create a YAML skeleton?

Yes, you can use issue numbers to create a YAML skeleton by providing the owner, repo, and issue_number as input. The tool accepts both full issue URLs and these separated identifiers.

How is the generated YAML file named and structured?

The generated YAML file is named setup-{ticket_id}.yaml and structured hierarchically. It compiles a complete description by extracting the ticket_id and task_name directly from the specified GitHub issue.

What is the best way to automate DevOps documentation from GitHub issues?

The best way to automate DevOps documentation from GitHub issues is parsing issue data to auto-generate a setup.yaml skeleton. This reduces manual document creation and provides a structured SSOT for development tasks.