file-issue

File GitHub issues with priority and area labels after deduplication.

5|1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dburkart/auto-engineer --skill file-issue-dburkart
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-issue
Source: https://github.com/dburkart/auto-engineer/tree/main/.claude/skills/file-issue
Command: npx skills add https://github.com/dburkart/auto-engineer --skill file-issue-dburkart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents unlabeled or incorrectly labeled GitHub issues by creating new issues with the right priority and classification labels immediately upon filing.

Core Features & Use Cases

  • Label-Taxonomy Enforcement: Applies exactly one priority:* label and the appropriate type/area labels on creation.
  • Backlog Deduplication: Searches open issues for overlaps and comments on an existing issue instead of filing duplicates.
  • Operational Workflow for Auto-Engineer: Captures follow-up work (e.g., TODOs and out-of-scope PR follow-ups) to keep the autonomous loop actionable.

Quick Start

Use the file-issue skill to file a new GitHub issue with triage-ready priority and area labels by invoking /file-issue with a clear title, motivation, work list, and relevant context.

Frequently Asked Questions about file-issue

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

FAQPage Schema
How do I automatically add priority and area labels to new GitHub issues?

Automatically triage GitHub issues by filing them with a strict label taxonomy that enforces exactly one priority label and the appropriate area classification upon creation.

What is the best way to prevent duplicate GitHub issues in an automated backlog workflow?

Prevent duplicate GitHub issues by searching open issues for overlapping content before filing, then commenting on the existing issue instead of creating a redundant entry.

How do I track TODOs and follow-up tasks from merged pull requests as GitHub issues?

Capture TODOs and out-of-scope pull request follow-ups by creating triage-ready GitHub issues with templated body sections to keep autonomous engineering loops actionable.

Do I need a specific GitHub setup to automate issue triage and deduplication?

Automated issue triage requires access to the GitHub MCP create_issue endpoint to apply prioritization taxonomies and search open issues for deduplication during autonomous workflows.

Why are my GitHub issues missing correct priority labels during autonomous filing?

Issues miss priority labels without taxonomy enforcement; this skill solves it by applying exactly one priority label and relevant area labels directly during issue creation.

Can I use automated issue filing for backlog management without creating duplicate tickets?

Backlog management automation uses deduplication against open issues to ensure overlapping follow-ups comment on existing tickets rather than generating duplicate noise.