skills.rest
ImperialAutomation
ImperialAutomationOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sync-closes

Analyze GitHub pull request descriptions and synchronize issue references in Closes statements.

11|3|Updated Jan 29, 2026
Search Tags:#automation#git#github#issue-tracking#pull-request#issue-closure
One-click install
npx skills add https://github.com/ImperialAutomation/claude-code-toolkit --skill sync-closes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-closes
Source: https://github.com/ImperialAutomation/claude-code-toolkit/tree/main/skills/sync-closes
Command: npx skills add https://github.com/ImperialAutomation/claude-code-toolkit --skill sync-closes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of ensuring that all sub-issues referenced in pull requests are properly listed in the "Closes" statements, preventing missed auto-closure of issues upon merge.

Core Features & Use Cases

  • PR Body Analysis: Fetches and reads the body of a specified pull request from GitHub.
  • Closes Statement Extraction: Parses existing "Closes" statements and identifies issues linked in the PR discussion and tracking tables.
  • Synchronization: Compares referenced issues to current "Closes" statements and suggests updates to include all relevant sub-issues and bugs.
  • Use Case: During a code review, automatically verify whether all relevant issues are set to close with the PR, and suggest necessary additions to the PR description.

Quick Start

Provide the PR number to the skill; it will retrieve the PR details, analyze the issues referenced, and suggest updates for the closing statements.

Frequently Asked Questions about sync-closes

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

FAQPage Schema
How do I automate issue closure synchronization for GitHub pull requests?▼

Automating issue closure synchronization requires analyzing PR descriptions and tracking tables to ensure all referenced sub-issues are included in the Closes statements. This prevents missed auto-closure of issues upon merge by verifying referenced issues match current closing statements.

Why are GitHub issues not auto-closing when I merge my pull request?▼

GitHub issues fail to auto-close when the pull request description omits them from the Closes statements. Synchronizing issue references involves parsing the PR body, extracting linked issues, and suggesting updates to include all relevant bugs before merging.

How do I check if all sub-issues are listed in a pull request's Closes statements?▼

Checking Closes statements involves fetching the pull request body, parsing existing closure references, and comparing them against issues linked in PR discussions and tracking tables to identify missing sub-issues that require addition.

Can I automatically verify issue tracking references in a pull request before merging?▼

Automatically verifying issue tracking references in a pull request involves analyzing the PR description and related issue lists. This process ensures all relevant issues are included in the Closes statements, reducing manual oversight during code review.

What is the best way to manage issue closure management across multiple GitHub pull requests?▼

Managing issue closure across GitHub pull requests involves coordinating the synchronization of issue references. By analyzing PR descriptions and comparing referenced issues to current Closes statements, the process suggests updates to include all relevant sub-issues and bugs.

Do I need to manually update pull request descriptions to fix missing issue closures?▼

Manual updates are unnecessary for fixing missing issue closures. By providing the PR number, the synchronization process retrieves details, analyzes referenced issues, and suggests necessary additions to the pull request description's closing statements automatically.

Related Skills

Explore More Software Engineering Skills→
EmergenceAIEmergenceAI
2

describe-pr

Generate pull request descriptions from GitHub API metadata and commit history.

Official
Advanced
khwerhahnkhwerhahn

close-issue

Close GitHub issues, linked pull requests, and feature branches.

Community
Advanced
wangqianCAIwangqianCAI

gh-issues

Automate GitHub issue resolution with parallel sub-agents for analysis, implementation, and testing.

Community
Advanced
kubiyabotkubiyabot
16

azure

Manage Azure resources via the native az CLI.

Official
Advanced