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

/create-github-issues-for-unmet-specification-requirements

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

Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.

Use this Skill: https://skilld.dev/gh/github/awesome-copilot/create-github-issues-for-unmet-specification-requirements

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

≈43 tokens for metadata: the name and description. ≈269 when used: this file.

Description uses 2.1% 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 ≈172 characters, or 2.1%.

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 Issues for Unmet Specification Requirements

Create GitHub Issues for unimplemented requirements in the specification at ${file}.

Process

  1. Analyze specification file to extract all requirements
  2. Check codebase implementation status for each requirement
  3. Search existing issues using search_issues to avoid duplicates
  4. Create new issue per unimplemented requirement using create_issue
  5. Use feature_request.yml template (fallback to default)

Requirements

  • One issue per unimplemented requirement from specification
  • Clear requirement ID and description mapping
  • Include implementation guidance and acceptance criteria
  • Verify against existing issues before creation

Issue Content

  • Title: Requirement ID and brief description
  • Description: Detailed requirement, implementation method, and context
  • Labels: feature, enhancement (as appropriate)

Implementation Check

  • Search codebase for related code patterns
  • Check related specification files in /spec/ directory
  • Verify requirement isn't partially implemented

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 automates the creation of GitHub issues by analyzing specification files and codebase status. It is safe for its intended purpose, though it lacks specific guardrails for handling potentially malicious instructions embedded in the specification files it processes.

  • 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
  • specification
  • requirements
  • automation
  • feature-request
  • workflow

README badge

README badge for github/awesome-copilot/create-github-issues-for-unmet-specification-requirements

Analyzes a specification file to extract unimplemented requirements and creates GitHub issues for each one, checking the codebase and existing issues to avoid duplicates. Useful for keeping a GitHub project's issue tracker synchronized with specification documents using the feature_request.yml template.

Generated from the current SKILL.md.

Does this skill create issues for all requirements or only unimplemented ones?
Only unimplemented requirements. The skill analyzes the specification file, checks the codebase for implementation status, and creates issues only for requirements that are not yet implemented.
Does this skill check for duplicate issues before creating new ones?
Yes. It searches existing issues using the search_issues function to avoid creating duplicates before submitting new issues.
What specification file formats does this skill support?
The skill references a specification file at ${file} but does not specify supported formats in the documentation. Clarify the file type (Markdown, JSON, etc.) with your team before use.
Does this skill use a custom issue template?
Yes, it uses a feature_request.yml template if available, with a fallback to GitHub's default issue template if the custom template does not exist.

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