Skip to main content
skill GitHub Copilot official · GitHub

create-github-issue-feature-from-specification — GitHub Copilot skill

This skill turns a specification file into a GitHub issue, checking for similar issues first. Use it when a feature request should cover the complete specification.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add github/awesome-copilot --skill create-github-issue-feature-from-specification -a claude-code
Open on GitHub

What create-github-issue-feature-from-specification does

The skill reads the specification at ${file} and extracts its requirements. It searches existing GitHub issues with search_issues; if a matching issue exists, it updates it with update_issue, otherwise it creates one with create_issue.

It uses the feature_request.yml template, falling back to the default template. The issue includes the feature name, problem statement, proposed solution, and context. Labels such as feature and enhancement are applied as appropriate. The skill creates one issue for the complete specification and limits its contents to changes the specification calls for.

Install it when you want to turn a full specification into a single GitHub issue. It is a poor fit when each requirement should become its own task.

What it helps with

  • turn requirements in a specification into a GitHub issue
  • check for matching issues before creating a request
  • update an existing issue instead of duplicating it
  • format a feature request with feature_request.yml

Example prompts for the agent

  • Create a GitHub issue from the specification at `${file}`.
  • Check for similar issues and update an existing one if there is a match.
  • Use `feature_request.yml` and apply the appropriate labels.

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

1Skills CLI (Vercel)

npx skills add github/awesome-copilot --skill create-github-issue-feature-from-specification -a claude-code

2Manually: put the files in place

~/.claude/skills/create-github-issue-feature-from-specification/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/create-github-issue-feature-from-specification/

Similar

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

How do I install create-github-issue-feature-from-specification in GitHub Copilot?

Run npx skills add github/awesome-copilot --skill create-github-issue-feature-from-specification. You can also use gh skill install github/awesome-copilot create-github-issue-feature-from-specification.

What does create-github-issue-feature-from-specification do?

It reads a specification, searches for similar GitHub issues, then creates an issue or updates a matching one. New issues use feature_request.yml when that template is available.

Does the skill create a separate issue for each requirement?

No. It creates one issue for the complete specification and includes only the changes that the specification requires.

Source text

SKILL.md · MIT
---
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)

© github · MIT · github/awesome-copilot

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor