What problem does it solve? After merge days or before releases, issue trackers accumulate stale open issues whose fixes already landed in merged pull requests. Manually reconciling PRs against issues is slow and error-prone, and naive automation closes issues on bare #N mentions or non-base merges, corrupting tracker state. ## Core Features & Use Cases - Authoritative close detection: Uses the tracker's closingIssuesReferences plus a configurable close-keyword regex (fix/close/resolve and custom keywords like "zamyka" or "behebt"), never acting on bare #N mentions. - Safe claim locking: Claims each issue with assignee, in-progress label, and claim comment before closing, and always releases the lock even on errors. - Dry-run and reporting: A --dry-run mode previews every planned mutation, and the final report surfaces unmatched issue mentions so teams can extend their closeKeywords config. - 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 since the last release, while leaving informational comments on issues whose PRs were closed unmerged or merged into non-base branches. ## Quick Start Ask the agent to run om-close-fixed-issues with --dry-run --since last-release to preview which tracker issues would be closed by recently merged pull requests.
