file-issue

Create GitHub issues with deduplication checks and label validation.

2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill file-issue-adamaltmejd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-issue
Source: https://github.com/adamaltmejd/registry-research-toolkit/tree/main/.agents/skills/file-issue
Command: npx skills add https://github.com/adamaltmejd/registry-research-toolkit --skill file-issue-adamaltmejd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent and unorganized issue tracking by enforcing strict repository hygiene and deduplication checks before any issue is created.

Core Features & Use Cases

  • Automated Deduplication: Automatically searches existing open and closed issues to prevent duplicate reports.
  • Hygiene Enforcement: Validates that every issue has exactly one area and one type label, and ensures proper relationship wiring to parent epics or follow-up sources.
  • Use Case: When a chief-of-staff needs to file a follow-up task from a pipeline merge-gate, this skill ensures the issue is correctly labeled, linked to the original PR, and checked against existing issues to maintain a clean project board.

Quick Start

Use the file-issue skill to process the draft located in the followups.md file and create a new GitHub issue if no duplicates are found.

Frequently Asked Questions about file-issue

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

FAQPage Schema
How do I automate GitHub issue creation while preventing duplicates?

Automating GitHub issue creation while preventing duplicates requires searching existing open and closed issues before filing. This skill uses custom Python scripts and the GitHub CLI to perform deduplication checks and validate metadata before creating new reports.

How does GitHub issue hygiene enforcement work for project management?

GitHub issue hygiene enforcement validates that every issue has exactly one area and one type label. It also ensures proper relationship wiring to parent epics or follow-up sources, applying strict metadata protocols to maintain a clean project board.

Do I need the GitHub CLI to automate issue tracking and apply labels?

Yes, you need the GitHub CLI installed to automate issue tracking with this skill. It relies on the gh dependency to perform secure repository searches, validate issue labels, and execute the automated creation of GitHub issues.

Can I link follow-up tasks to a pull request when filing GitHub issues?

Yes, you can link follow-up tasks to a pull request when filing GitHub issues. The skill ensures provenance tracking by wiring parent-child relationships, correctly linking the new issue to the original PR or parent epic during creation.

What is the best way to enforce consistent labeling across GitHub issues?

The best way to enforce consistent labeling across GitHub issues is through automated validation scripts. This skill checks that every issue receives exactly one area and one type label, preventing inconsistent categorization on your project board.

Why does my automated issue tracking fail to maintain a clean project board?

Automated issue tracking fails to maintain a clean project board when it lacks deduplication and strict metadata hygiene. Without validating labels and checking existing issues before creation, duplicate reports and unlinked tasks clutter the repository.