file-finding

Create GitHub issues for defects with deduplication and labels.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/EtaCassiopeia/claude-skills --skill file-finding
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-finding
Source: https://github.com/EtaCassiopeia/claude-skills/tree/main/config/skills/file-finding
Command: npx skills add https://github.com/EtaCassiopeia/claude-skills --skill file-finding

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the process of filing GitHub issues for defects and gaps discovered during implementation or review, ensuring they are properly documented and triaged.

Core Features & Use Cases

  • Deduplication: Checks for existing issues to avoid duplicates and maintain issue quality.
  • Labeling: Automatically applies 'agent-found' and 'needs-triage' labels for proper issue handling.
  • Documentation: Provides a structured template for issue creation, including problem description, evidence, and proposed fix.
  • Use Case: When reviewing a pull request, if you encounter a defect that is out of scope, use this Skill to create a GitHub issue with all necessary details.

Quick Start

/file-finding "A bug was found in the 'calculate' function that causes incorrect results."

Frequently Asked Questions about file-finding

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

FAQPage Schema
How do I automate GitHub issue creation for defects found during a pull request review?

Automating GitHub issue creation for defects involves checking for duplicates, applying 'agent-found' and 'needs-triage' labels, and generating a structured template. This ensures out-of-scope bugs are properly documented and triaged without manual entry.

Does this issue tracking automation require GitHub API access and Bash scripting?

Yes, this issue tracking automation requires GitHub API access and Bash scripting capabilities. It relies on the 'gh' command-line tool to interact with repositories, check existing issues, and submit new defect reports programmatically.

What is the best way to avoid duplicate bug reporting when filing GitHub issues?

The best way to avoid duplicate bug reporting is to automatically check existing GitHub issues before creating a new one. This deduplication step maintains issue quality by ensuring no redundant defect reports are submitted to the repository.

Can I use a structured template for documenting gaps and defects on GitHub?

Yes, you can use a structured template for documenting gaps and defects on GitHub. The automation provides a standardized format including problem description, evidence, and proposed fix, ensuring all necessary details are captured for proper triage.

How does automatic labeling work for newly filed GitHub issues?

Automatic labeling for newly filed GitHub issues works by applying specific tags like 'agent-found' and 'needs-triage' upon creation. This ensures that defects and gaps are immediately categorized for proper issue handling and prioritization by maintainers.