gh-report

Files deduplicated bug reports and feature requests on external GitHub repositories following their intake rules.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/coseto6125/claude-setup --skill gh-report-coseto6125
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-report
Source: https://github.com/coseto6125/claude-setup/tree/main/skills/gh-report
Command: npx skills add https://github.com/coseto6125/claude-setup --skill gh-report-coseto6125

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Filing issues or PRs against repositories you do not own often fails: maintainers auto-close external issues, route reports through Discussions, or reject unsolicited PRs. This Skill discovers each repo's actual intake channel and drafts reports that match its templates before anything is posted. ## Core Features & Use Cases - Dedupe before drafting: Searches existing Issues and Discussions with multiple keyword variants, and checks the default branch source to confirm the defect still exists. - Intake rule discovery: Reads CONTRIBUTING.md, ISSUE_TEMPLATE config, and contact links to determine whether reports belong in Issues, Discussions, or nowhere. - Template-conformant drafting: Writes one section per form field with version, OS, repro steps, and expected versus actual behavior, then posts only after explicit user approval. - Use Case: You hit a bug in an open-source CLI tool. The Skill searches for duplicates, finds the repo auto-closes external issues, and posts a properly formatted report to the correct Discussions category instead. ## Quick Start Use the gh-report skill to check whether this bug has already been reported upstream and file it with the repository following its contribution rules.

Frequently Asked Questions about gh-report

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

FAQPage Schema
How do I report a bug to a GitHub repository I don't own?▼

Search existing Issues and Discussions first to avoid duplicates, then read the repo's CONTRIBUTING.md and issue templates to find the accepted intake channel. Draft your report to match the template's exact fields and confirm with the maintainer's rules before posting.

How to check if a bug was already reported on GitHub?▼

Run gh search issues with 2 to 4 keyword variants covering symptom words, component names, and exact error strings. Also scan Discussions via the GitHub API, and fetch the relevant source file from the default branch to confirm the defect still exists.

What should I do when a repo auto-closes external issues?▼

Check .github/ISSUE_TEMPLATE/config.yml for contact_links, which name the real intake channel, usually a Discussions category. Post your report there instead, reshaped to the template's required fields such as problem, proposed solution, and repro steps.

Can I open a PR on an external open-source project?▼

Only if the repo's CONTRIBUTING.md permits external PRs. Many projects restrict PRs to maintainers or vouched contributors and give unsolicited PRs no review, in which case you should present findings as an issue or discussion instead.

What information should a good upstream bug report include?▼

Include the tool's version output, operating system, minimal reproduction steps, and expected versus actual behavior, organized under the exact headings of the repo's issue form. Redact tokens and secrets, and write in English unless the repo uses another language.