file-issue

Create structured GitHub issues from bug and feature templates with labels.

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/lleontor705/cortex-ia --skill file-issue-lleontor705
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-issue
Source: https://github.com/lleontor705/cortex-ia/tree/main/internal/assets/skills/file-issue
Command: npx skills add https://github.com/lleontor705/cortex-ia --skill file-issue-lleontor705

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates GitHub issues using required templates (bug report or feature request) and enforces issue-first workflows with proper labeling to ensure consistency and traceability across projects.

Core Features & Use Cases

  • Enforces the use of bug_report.yml and feature_request.yml templates for new issues.
  • Automatically applies the status:needs-review label on creation.
  • Returns the issue URL and metadata to the caller for traceability.
  • Redirects questions to GitHub Discussions when appropriate.

Quick Start

Create a new issue using the appropriate template and fill all required fields to generate a tracked GitHub issue.

Frequently Asked Questions about file-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce structured GitHub issues with templates for bugs and feature requests?▼

Enforce structured GitHub issues by automating issue filing with bug_report.yml and feature_request.yml templates. This ensures consistency, applies the status:needs-review label automatically, and returns the issue URL and metadata for traceability across projects.

Can I automatically apply labels to GitHub issues when they are created?▼

Yes, automatically apply labels to GitHub issues upon creation. The workflow specifically applies the status:needs-review label to every new issue generated from the bug report or feature request templates, ensuring proper tracking and review.

What is an issue-first workflow and how do templates support it?▼

An issue-first workflow requires all bugs and features to be tracked as structured GitHub issues before development begins. Using bug_report and feature_request templates enforces this by standardizing inputs, applying status:needs-review, and redirecting general questions to Discussions.

Does this GitHub issue automation support feature requests and bug reports differently?▼

This GitHub issue automation supports both feature requests and bug reports equally by enforcing their respective templates, feature_request.yml and bug_report.yml. Both issue types receive the status:needs-review label upon creation and return traceable metadata.

When should I redirect questions to GitHub Discussions instead of filing an issue?▼

Redirect questions to GitHub Discussions instead of filing an issue when the inquiry does not fit the bug_report or feature_request templates. This maintains an issue-first workflow by keeping the GitHub issue tracker strictly for structured bugs and feature requests.