sync-merged-pr-issues

Reconcile merged pull requests with GitHub issues and post comments.

Updated May 31, 2026

Search Tags:#automation #GitHub #issue tracking #post-merge #PR reconciliation

Ready to run

npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill sync-merged-pr-issues

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-merged-pr-issues
Source: https://github.com/zizzfizzix/agentic-engineering-framework/tree/main/core/ai/skills/sync-merged-pr-issues
Command: npx skills add https://github.com/zizzfizzix/agentic-engineering-framework --skill sync-merged-pr-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps automate the process of reconciling merged and closed pull requests with GitHub issues, streamlining post-merge housekeeping.

Core Features & Use Cases

Automated Issue Closure: Closes GitHub issues that are authoritatively fixed by merged pull requests.
Info Comments on Unmerged PRs: Posts informational comments on issues when their PRs were closed without merging.
Use Case: Before tagging a release, this skill can help ensure all issues are up to date with the current state of merged pull requests.

Quick Start

Run the sync-merged-pr-issues skill to process merged and closed pull requests from the past week.

Frequently Asked Questions about sync-merged-pr-issues

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

FAQPage Schema

How do I automate GitHub issue closure when pull requests are merged?▼

This skill automates GitHub issue closure post-merge by identifying issues authoritatively fixed by merged pull requests and closing them. It processes recent PRs to reconcile their state with linked issues.

What happens to GitHub issues when a pull request is closed without merging?▼

When a pull request is closed without merging, this skill posts informational comments on the linked GitHub issues. This keeps issue tracking transparent by explaining why the proposed fix was not applied.

Do I need GitHub API access to automate issue reconciliation for merged PRs?▼

Yes, you need GitHub API access to automate issue reconciliation for merged PRs. The skill requires this access to read pull request states, post comments, and manage issue states while respecting claim locks.

How do I ensure all GitHub issues are updated before tagging a release?▼

To ensure all GitHub issues are updated before tagging a release, this skill processes merged and closed pull requests from the past week. It reconciles issue states to match the current state of merged PRs.

Does this issue reconciliation tool respect existing claim locks on GitHub issues?▼

Yes, this issue reconciliation tool respects claim locks for GitHub issue state management. It ensures automated closure and commenting do not override existing claim locks during post-merge processing.