PluginBench
Skill
Official
Review
Audit score 70

create-github-issue-feature-from-specification

github/awesome-copilot

Turn a spec file into a well-formed GitHub feature request issue automatically.

What is create-github-issue-feature-from-specification?

This skill automates creating a GitHub Issue for a feature request based on a specification file. It extracts requirements from the spec, checks for existing duplicate issues, and creates or updates an issue using the feature_request.yml template.

  • Analyzes a specification file to extract feature requirements
  • Searches existing GitHub issues to avoid duplicates
  • Creates a new GitHub issue using the feature_request.yml template (or default fallback)
  • Updates an existing issue if one already matches the specification
  • Applies appropriate labels like feature and enhancement
  • Writes a clear title and description including problem statement, proposed solution, and context

How to install create-github-issue-feature-from-specification

npx skills add https://github.com/github/awesome-copilot --skill create-github-issue-feature-from-specification
Prerequisites
  • Access to GitHub repository with issue creation permissions
  • GitHub MCP tools (search_issues, create_issue, update_issue) available to the agent
  • A specification file describing the feature request
  • Optional: a feature_request.yml issue template in the repository
Claude Code
Cursor
Windsurf
Cline

How to use create-github-issue-feature-from-specification

  1. 1.Provide the path to a specification file (${file}) describing the feature
  2. 2.The skill analyzes the specification to extract requirements
  3. 3.It searches existing GitHub issues using search_issues to check for duplicates
  4. 4.It creates a new issue with create_issue (using feature_request.yml template, or default if unavailable) or updates an existing issue with update_issue
  5. 5.Review the created/updated issue for title, description, and labels accuracy

Use cases

Good for
  • Convert a written feature specification document into a GitHub issue
  • Avoid creating duplicate feature request issues by checking existing ones first
  • Standardize feature request issues using a consistent template
  • Update an existing feature request issue when a specification changes
Who it's for
  • Developers managing feature specifications who need GitHub issues created
  • Product managers translating specs into tracked GitHub issues
  • Teams using GitHub Copilot/agents for repository workflow automation

create-github-issue-feature-from-specification FAQ

Does this skill prevent duplicate issues?

Yes, it checks existing issues using search_issues before creating a new one, and can update an existing issue instead of creating a duplicate.

What template does it use for the issue?

It uses the feature_request.yml template, falling back to the default issue template if that is not available.

What tools does this skill require access to?

It relies on GitHub issue-related tools: search_issues, create_issue, and update_issue.

What labels are applied to created issues?

It applies labels such as 'feature' and 'enhancement' as appropriate, based on the specification content.

Full instructions (SKILL.md)

Source of truth, from github/awesome-copilot.


name: create-github-issue-feature-from-specification description: 'Create GitHub Issue for feature request from specification file using feature_request.yml template.'

Create GitHub Issue from Specification

Create GitHub Issue for the specification at ${file}.

Process

  1. Analyze specification file to extract requirements
  2. Check existing issues using search_issues
  3. Create new issue using create_issue or update existing with update_issue
  4. 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)