ot-close-fixed-issues

Close tracker issues that recently merged pull requests authoritatively fixed.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-close-fixed-issues-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-close-fixed-issues
Source: https://github.com/triage-software/skills/tree/main/skills/ot-close-fixed-issues
Command: npx skills add https://github.com/triage-software/skills --skill ot-close-fixed-issues-triage-software

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 teams to manually reconcile PRs against issues before every release. This Skill automates that reconciliation by scanning recent pull requests and closing only the issues with authoritative fix links. ## Core Features & Use Cases - Authoritative close detection: Uses the tracker's closingIssuesReferences plus configurable close keywords (fixes/closes/resolves and custom non-English keywords), never acting on bare #N mentions. - Safe claim-and-release locking: Claims each issue with an assignee, in-progress label, and claim comment before closing, and always releases the lock even on error. - Dry-run and gap reporting: --dry-run previews every planned mutation, and unmatched issue mentions are surfaced so teams can extend closeKeywords. - Use Case: Before tagging a release, run the skill with --since last-release to close every issue fixed by PRs merged into the base branch and comment on issues whose PRs were closed unmerged or merged into a non-base branch. ## Quick Start Ask the agent to run ot-close-fixed-issues with --dry-run to preview which tracker issues the recently merged PRs would close.

Frequently Asked Questions about ot-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 PRs?▼

Run this skill over a window of recent pull requests; it reads closingIssuesReferences and close keywords like fixes or closes, then closes each matching open issue with a linked comment. Use --since last-release or an ISO date to bound the window.

How to preview issue closures before actually closing them?▼

Pass the --dry-run flag. The skill prints every mutation it would make, prefixed with DRY-RUN:, without posting comments, closing issues, or changing labels or assignees.

Does it support non-English closing keywords in PR bodies?▼

Yes. Add a closeKeywords array to .ai/agentic.config.json with single-word keywords such as zamyka or behebt. These extend the built-in English keywords and are matched case-insensitively with the same adjacency rule before #N.

Will it close issues referenced only by a bare #N mention?▼

No. Bare #N mentions are treated as conversational references, never close links. Such unmatched mentions are resolved and reported as a diagnosis so teams can extend closeKeywords, but no issue is closed or commented on.

What happens when a fixing PR was closed without merging?▼

The issue is not closed. The skill posts an informational comment noting the PR closed without merge, and links a replacement PR when one in the same window declares Supersedes #N.

Can it act on issues in other repositories?▼

No. Cross-repository issue references are explicitly out of scope. Every read and mutation is scoped to the resolved repository, and cross-repo references are skipped and logged.