Cluster GitHub issues by title similarity and build a FAQ section from the top recurring questions with synthesized answers.
Pulls all closed GitHub issues for a repo, clusters them by title similarity, and produces a FAQ document for the top-N recurring questions. Each FAQ entry includes a one-paragraph answer synthesized from the resolution comments of the cluster.
repo: <owner>/<name>.top_n: number of FAQ entries to produce (default 10).since_days: only include issues closed in the last N days (default 365).GITHUB_TOKEN env var.gh issue list --repo <repo> --state closed --limit 1000 --search "closed:>=<date>" --json number,title,body,labels,comments.top_n.reactions.total_count).#NNN links.docs/FAQ.md.docs/FAQ.md containing a numbered list of FAQ entries: question (H3), answer paragraph, "Source issues:" footer linking back to GitHub. Stdout prints cluster sizes for transparency.
Sample three entries: open the linked source issues and confirm the synthesized answer matches the resolution direction (not necessarily verbatim, but no contradictions). Re-run the cluster step with top_n + 5 and verify entries 1..top_n remain stable — non-stable rankings suggest tighter clustering threshold needed. If gh issue list returned fewer than 100 issues, prepend a "small sample" note to the FAQ header.
dependencies or by author bot suffix.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/faq-from-issue-tracker.
Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Diff two OpenAPI YAML files and produce a backwards-compatibility changelog grouped into breaking, non-breaking, and additive changes.
Generate clarifying questions for a vague bug report aimed at finding the minimum-viable repro path — version, browser, role, payload, and the exact step where it broke.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.
Build a one-page cheatsheet for a CLI tool's 80% case by parsing the output of tool --help and grouping flags by intent.
Document every env var declared in .env.example and config files, cross-referenced to the code locations that read each one.