create-github-issue-feature-from-specification

Create or update GitHub Issues from feature specification files using feature_request.yml.

Updated Mar 18, 2026

Search Tags:#automation #workflow #template #github #specification #issue

Ready to run

npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-github-issue-feature-from-specification-angryconsultant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-github-issue-feature-from-specification
Source: https://github.com/angryconsultant/Copilot-CLI/tree/main/skills/create-github-issue-feature-from-specification
Command: npx skills add https://github.com/angryconsultant/Copilot-CLI --skill create-github-issue-feature-from-specification-angryconsultant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates GitHub Issue creation for a feature specification file, ensuring a consistent and traceable bridge between specification documents and project management.

Core Features & Use Cases

Analyze a feature specification file to extract actionable requirements.
Create a new GitHub Issue or update an existing one to prevent duplicates.
Apply the feature_request.yml template by default, with a fallback to a standard issue format when needed.

Quick Start

Use the skill on a specification file to automatically create or update the corresponding GitHub Issue.

Frequently Asked Questions about create-github-issue-feature-from-specification

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

FAQPage Schema

How do I automatically create GitHub issues from a feature specification file?▼

You can automatically create GitHub issues from a specification file by using an automation workflow that analyzes the spec, checks for existing issues to prevent duplicates, and applies the feature_request.yml template to format the content. This ensures a single, traceable issue per specification.

How does issue automation handle duplicate GitHub issues for the same specification?▼

Issue automation prevents duplicates by checking for existing GitHub issues linked to the specification before creating a new one. If an issue already exists, the workflow updates it with the latest spec analysis instead of generating a duplicate entry.

Can I use a custom template like feature_request.yml for automated GitHub issue creation?▼

Yes, automated GitHub issue creation applies the feature_request.yml template by default to format the extracted specification requirements. If the template is unavailable, the workflow falls back to a standard issue format to ensure the content is still published.

What is the best way to keep GitHub issues synchronized with feature specification documents across repositories?▼

The best way to synchronize GitHub issues with feature specifications across repositories is to apply an automation workflow that analyzes the spec file and creates or updates the corresponding issue. This maintains a consistent and traceable bridge between documents and project management.

Do I need a specific issue template format to automate GitHub issue creation from specs?▼

You do not need a strict issue template format because the automation workflow defaults to feature_request.yml but includes a fallback to a standard issue format. This allows you to extract actionable requirements from specifications even if the custom template is missing.

When should I avoid automating GitHub issue creation from specification files?▼

You should avoid automating GitHub issue creation if your specification files lack structured, actionable requirements or if your repository lacks a feature_request.yml template and requires complex custom formatting that a standard issue format fallback cannot accommodate.