Source profileQuality 63/100

github/awesome-copilot/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md

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

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

Source repository stars
37,126
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/github/awesome-copilot --skill "skills/create-github-issues-for-unmet-specification-requirements"
    Safe inspection promptEditorial

    Inspect the Agent Skill "create-github-issues-for-unmet-specification-requirements" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/create-github-issues-for-unmet-specification-requirements/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Process

      1. Analyze specification file to extract all requirements 2. Check codebase implementation status for each requirement 3. Search existing issues using searchissues to avoid duplicates 4. Create new issue per unimplemented requirement using createissue 5. Use featurerequest.yml t…

      Analyze specification file to extract all requirementsCheck codebase implementation status for each requirementSearch existing issues using searchissues to avoid duplicates
    2. 02

      Implementation Check

      Search codebase for related code patterns

      Search codebase for related code patternsCheck related specification files in /spec/ directoryVerify requirement isn't partially implemented
    3. 03

      Requirements

      One issue per unimplemented requirement from specification

      One issue per unimplemented requirement from specificationClear requirement ID and description mappingInclude implementation guidance and acceptance criteria

    Permission review

    Static risk signals and limitations

    No configured static risk pattern was detected

    This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score63/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars37,126SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guidecatalog recordEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    github/awesome-copilot
    Skill path
    skills/create-github-issues-for-unmet-specification-requirements/SKILL.md
    Commit
    9933dcad5be5caeb288cebcd370eeeb2fc2f1685
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    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