create-github-issue-feature-from-specification

Create GitHub issues from specification files with duplicate checking.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Cripacx/agentic-dotnet --skill create-github-issue-feature-from-specification-cripacx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-issue-feature-from-specification
Source: https://github.com/Cripacx/agentic-dotnet/tree/main/skills/create-github-issue-feature-from-specification
Command: npx skills add https://github.com/Cripacx/agentic-dotnet --skill create-github-issue-feature-from-specification-cripacx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating GitHub issues for new features by automatically parsing specification files and checking for duplicates.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues directly from specification files.
  • Duplicate Checking: Analyzes existing issues to prevent redundant entries.
  • Use Case: You've just finalized a feature specification document. Use this Skill to create a well-formatted GitHub issue, ensuring all requirements are captured and no duplicate issues already exist.

Quick Start

Use the create-github-issue-feature-from-specification skill to create a GitHub issue from the file 'feature_spec.yml'.

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 create GitHub issues from a feature specification file?

To create GitHub issues from a specification file, the skill parses your spec to extract requirements and generates a formatted issue. It automates this process by analyzing specification files and creating well-structured GitHub issues using a 'feature_request.yml' template.

Can I automatically check for duplicate GitHub issues before creating a new feature request?

Yes, you can automatically check for duplicate GitHub issues before creating a new feature request. The skill searches existing issues within your repository to identify similar entries, preventing redundant issue creation by updating an existing issue instead of opening a new one.

What is the best way to automate feature request issue tracking on GitHub using specification documents?

The best way to automate feature request issue tracking using specification documents is to use a skill that parses your specs and applies standardized templates. This ensures clear titles, descriptions, and appropriate labels are automatically applied to your GitHub issues.

How does the skill handle issue content if the feature_request.yml template is missing?

If the feature_request.yml template is missing, the skill falls back to a default format for issue content. This fallback mechanism ensures that feature requests are still created with clear titles, descriptions, and appropriate labels even without the specific template.

Do I need a specific format for my specification files to generate GitHub issues?

You need a structured specification file like 'feature_spec.yml' to generate GitHub issues accurately. The skill analyzes these specification files to extract requirements, checking for existing similar issues before creating a new issue or updating an existing one.