skills.rest
go-musicfox
go-musicfoxOFFICIAL
Explore all skills by this author →
WebsiteGitHub

om-close-fixed-issues

Close tracker issues that recently merged pull requests authoritatively fixed.

2.6k|159|Updated Mar 8, 2021
Search Tags:#automation#github#issue tracker#maintenance#pull requests#release housekeeping#close issues
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-close-fixed-issues-go-musicfox
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-close-fixed-issues
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-close-fixed-issues
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-close-fixed-issues-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After merges, issue trackers accumulate stale open issues that were actually fixed by merged PRs, forcing maintainers to manually reconcile PRs against issues before every release. This Skill automates that reconciliation safely, closing only issues with authoritative close links and never acting on ambiguous references. ## Core Features & Use Cases - Authoritative close detection: Uses the tracker's closingIssuesReferences plus a configurable close-keyword regex (built-in English keywords extended by closeKeywords in .ai/agentic.config.json), and never acts on bare #N mentions. - Safe branching by PR state: Closes issues only when the PR merged into the base branch; posts informational comments instead when the PR merged into a non-base branch or was closed without merging. - Claim locking and dry-run support: Claims issues with assignee plus in-progress label before mutating, releases locks even on error, respects do-not-close/blocked labels, and supports --dry-run to preview every planned mutation. - Unmatched-mention reporting: Surfaces PRs that mention issues without a recognized close keyword (common in non-English repositories) so teams can extend closeKeywords instead of silently reporting closed 0. - Use Case: Before tagging a release, run the skill with --since last-release to flush every issue fixed since the last release, with a full audit table of what was closed, commented, or skipped and why. ## Quick Start Ask the agent to run om-close-fixed-issues with --since last-release and --dry-run to preview which tracker issues recent merged PRs would close.

Frequently Asked Questions about om-close-fixed-issues

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

FAQPage Schema
How do I automatically close GitHub issues fixed by merged pull requests?▼

Run this skill with a --since window; it lists recently merged PRs, reads their closingIssuesReferences and close keywords like fixes or resolves, then closes each referenced open issue with a comment linking the PR and merge commit.

How to close issues when PR bodies are written in a non-English language?▼

Add your language's close terms to the closeKeywords array in .ai/agentic.config.json, for example zamyka or naprawia. These extend the built-in English keywords, and the run report shows unmatched mentions so you know which terms to add.

Does it close issues referenced only by a bare #N mention in a PR?▼

No. Bare #N mentions are treated as conversational references, not close links. The skill requires closingIssuesReferences or an explicit close keyword followed by #N, and reports unmatched mentions separately without mutating them.

What happens when a PR was closed without merging or merged into a non-base branch?▼

The issue is never closed in those cases. The skill posts an informational comment explaining the PR was closed unmerged (with a superseded-by link when detected) or merged into a non-base branch, leaving the issue open.

Can I preview the changes before any issue is closed or commented on?▼

Yes, pass --dry-run to print every planned mutation prefixed with DRY-RUN without posting comments, closing issues, or changing labels. The unmatched-mentions diagnosis section is also printed during dry runs.

How does it avoid conflicting with other automation running on the same issues?▼

It claims each issue with an assignee, an in-progress label, and a claim comment before acting, skips issues already claimed by others or labeled do-not-close or blocked, and always releases its locks even on error.

Related Skills

Explore More Software Engineering Skills→
tkoguttkogut
1

om-close-fixed-issues

Close tracker issues that merged pull requests authoritatively fixed and comment on unresolved ones.

Community
Advanced
andreciniandrecini
2

write-changelog-entry

Generate a new CHANGELOG.md release entry from merged pull requests and commits.

Community
Intermediate
dsifrydsifry
7

pr-shepherd

Monitor GitHub pull requests and resolve CI failures until merge.

Community
Advanced
Pythagora-ioPythagora-io
9

linear-ticket-cleanup

Remove Linear ticket worktrees, branches, and feature directories after completion.

Official
Intermediate