GitHub Issue Triage

Use find_closable.sh to identify issues marked as implemented or resolved against your codebase and design docs. The script surfaces candidates by matching issue metadata against CHANGELOG references and repository config, letting you review or auto-close them in bulk.

Run match_design_docs.sh to connect open issues to your design_docs metadata. The script cross-references issue descriptions and labels with your planning documents, surfacing gaps where issues lack corresponding design coverage or vice versa.

Generate a triage report using triage_report.sh to get a comprehensive view of all open issues, their age, labels, and implementation status. Use this output during backlog planning and release readiness to prioritize work and surface stale or duplicate issues.

Yes. Run find_closable.sh with the --close flag to automatically close issues the script identifies as implemented. The tool relies on GitHub CLI (gh) and jq to match issues against CHANGELOG entries and local design_docs, then execute closures.

Design docs enhance matching but aren't strictly required. The Skill can list and age-sort open issues with list_open_issues.sh using only GitHub CLI. Design doc matching is optional and surfaces alignment gaps; skip it if your workflow doesn't track design separately.

Use list_open_issues.sh to get a sorted view of every open issue with labels, age, and status metadata. This is a lightweight first step before running full triage or closure workflows.