Create GitHub Issue for feature request from specification file using feature_request.yml template.
v1.0LATEST
NewUpdated Jun 26, 2026
Create GitHub Issue from Specification
Create GitHub Issue for the specification at ${file}.
Process
Analyze specification file to extract requirements
Check existing issues using search_issues
Create new issue using create_issue or update existing with update_issue
Use feature_request.yml template (fallback to default)
Requirements
Single issue for the complete specification
Clear title identifying the specification
Include only changes required by the specification
Verify against existing issues before creation
Issue Content
Title: Feature name from specification
Description: Problem statement, proposed solution, and context
Labels: feature, enhancement (as appropriate)
Files1
1 files · 1.0 KB
Select a file to preview
Overall Score
38/100
Grade
D
Below Average
Grades are signals, not a certification. Always review a skill yourself before use.
Safety
75
Quality
22
Clarity
48
Completeness
15
Summary
This skill guides an agent to create GitHub Issues from feature specification files. It analyzes a specification, checks for duplicate issues, and creates or updates a single GitHub Issue with structured content including title, description, and appropriate labels.
Detected Capabilities
GitHub API read (search_issues)GitHub API write (create_issue, update_issue)File read (specification analysis)Template processing (feature_request.yml)
Trigger Keywords
Phrases that agents use to match this skill to user intent.
create github issuegithub feature requestissue from specificationconvert spec to issuegithub issue automation
Use Cases
Convert feature specifications into GitHub Issues for tracking
Prevent duplicate feature requests by searching existing issues
Standardize feature issue creation using feature_request.yml template
Organize feature requests with consistent labeling (feature, enhancement)
Quality Notes
Skill is extremely brief and lacks implementation detail — no examples of how to extract requirements from specifications
No guidance on specification file format (YAML, Markdown, JSON, etc.)
No error handling documented — what if specification is malformed? What if search returns too many results?
No information on how to determine when to create vs. update existing issues
The fallback mechanism for 'feature_request.yml template' is not explained
Missing guidance on handling edge cases: empty specifications, multiple features in one file, or specification files with no clear title
No mention of required GitHub authentication or permissions
Process description is vague — step 2 mentions 'search_issues' but doesn't explain what query to use or how to detect true duplicates
Model: claude-haiku-4-5-20251001Analyzed: Jun 26, 2026
Reviews
Add this skill to your library to leave a review.
No reviews yet
Be the first to share your experience.
Use github/create-github-issue-feature-from-specification in your dev environment — a Developer account adds skills to your library and syncs them via the SkillRepo CLI.