Index of every page on this site: llms.txt
All skills
github avatar

/create-github-issue-feature-from-specification

@f10fdb8 official
by githubgithub/awesome-copilot41k stars
5,399
Run it yourself

Create GitHub Issue for feature request from specification file using feature_request.yml template.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/create-github-issue-feature-from-specification

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈37 tokens for metadata: the name and description. ≈184 when used: this file.

Description uses 1.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈148 characters, or 1.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill processes user-provided specification files to create or update GitHub issues without adequate input sanitization, creating a surface for indirect prompt injection.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer8mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f10fdb8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 9 months ago
  • github
  • issues
  • feature-request
  • automation
  • specification
  • templates

README badge

README badge for github/awesome-copilot/create-github-issue-feature-from-specification

Creates a GitHub issue from a specification file, extracting requirements and checking for duplicates before submission. Uses the feature_request.yml template to populate title, description, and labels based on the specification content.

Generated from the current SKILL.md.

What specification file formats does this skill support?
The skill analyzes specification files but does not specify supported formats in the SKILL.md. It assumes a file exists at `${file}` and extracts requirements from it.
Does this skill check for duplicate issues before creating?
Yes. The skill uses `search_issues` to check existing issues and will update an existing issue instead of creating a duplicate if one matches the specification.
What template does this skill use for the GitHub issue?
The skill uses the `feature_request.yml` template if available, falling back to GitHub's default template otherwise.
Can this skill modify an existing GitHub issue?
Yes. If an issue matching the specification already exists, the skill will update it using `update_issue` instead of creating a new one.

Generated from the current SKILL.md. These answers refresh after source changes.