skills.rest
psaab
psaabCOMMUNITY
Explore all skills by this author →
GitHub

sync-history

Synchronize GitHub issue and pull request metadata into local Markdown files.

8|2|Updated Feb 8, 2026
Search Tags:#automation#documentation#github#sync#issue-tracking#pull-requests
One-click install
npx skills add https://github.com/psaab/xpf --skill sync-history
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-history
Source: https://github.com/psaab/xpf/tree/main/.claude/skills/sync-history
Command: npx skills add https://github.com/psaab/xpf --skill sync-history

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, python3.

What problem does it solve?

This Skill solves the problem of documentation drift by ensuring that local records of project issues and pull requests remain perfectly synchronized with the live state of the GitHub repository.

Core Features & Use Cases

  • Automated Issue Tracking: Generates a comprehensive, categorized history of all issues, including status and descriptions.
  • PR Documentation: Compiles a complete log of all pull requests, including merge status and branch information.
  • Use Case: After a major release or a busy development sprint, run this skill to automatically update your project documentation files so that stakeholders have an accurate, offline-accessible record of all recent activity.

Quick Start

Run the sync-history skill to regenerate the issue and pull request history files and commit the changes to the repository.

Frequently Asked Questions about sync-history

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

FAQPage Schema
How do I sync GitHub issues and pull requests with local Markdown documentation?▼

Syncing GitHub issues and pull requests with Markdown documentation requires the GitHub CLI to fetch repository data and Python 3 to process JSON responses and format local project history files.

What is the best way to automate documentation updates for GitHub issue tracking?▼

Automating documentation updates for GitHub issue tracking is done by querying the GitHub CLI for all issue statuses and descriptions, then generating categorized Markdown files to prevent documentation drift.

Do I need the GitHub CLI and Python 3 to document pull request history?▼

Yes, you need the GitHub CLI to query pull request metadata and Python 3 to process the JSON responses and format the output files for local documentation.

Can I generate an offline record of all merged pull requests and closed issues?▼

Yes, you can generate an offline record of all merged pull requests and closed issues by querying the GitHub CLI and formatting the output into local Markdown files for stakeholder access.

Why does my project history documentation drift from the live GitHub repository state?▼

Project history documentation drifts from the live GitHub repository state when local records are updated manually, which you can prevent by synchronizing issue and pull request metadata automatically.

Related Skills

Explore More Software Engineering Skills→
myaiartist360-makermyaiartist360-maker

github

Manage GitHub repositories, pull requests, and CI/CD via the gh CLI.

Community
Intermediate
sobhanashinesobhanashine
1

document-release

Update markdown documentation files after shipping new versions.

Community
Advanced
byunghak-dablebyunghak-dable

github-pr-push

Push code changes and create or update GitHub Pull Requests with automated checks.

Community
Advanced
BasedHardwareBasedHardware
13.1k

omi-api-integration

Guide Omi API integration with OAuth, MCP, and webhooks.

Official
Advanced