skills.rest
ShareX
ShareXOFFICIAL
Explore all skills by this author →
Website𝕏@ShareXGitHub

xip-sync

Synchronize GitHub XIP issues into Markdown backups in tasks/.

309|15|Updated Dec 29, 2025
Search Tags:#automation#github#backup#issues#tasks#workflows#xip
One-click install
npx skills add https://github.com/ShareX/XerahS --skill xip-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: xip-sync
Source: https://github.com/ShareX/XerahS/tree/main/.ai/skills/xip-sync
Command: npx skills add https://github.com/ShareX/XerahS --skill xip-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Create and maintain XerahS Improvement Proposals (XIPs) using GitHub as the source of truth and a local tasks/ backup for offline reference. Syncing ensures the official content stays in GitHub while preserving an auditable, recoverable backup.

Core Features & Use Cases

  • GitHub as source of truth: XIPs are authored and tracked as issues with the label xip.
  • Backup in tasks/: A single-folder Markdown backup stores one file per XIP for offline access and archival.
  • Sync workflows: Keep GitHub issues and local backups in sync via dedicated PowerShell scripts.
  • Recovery & migration: Convert legacy XIP files back into GitHub issues if needed.

Quick Start

From the repository root, run the PowerShell script to sync GitHub XIP issues into tasks/ as Markdown backups.

Frequently Asked Questions about xip-sync

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

FAQPage Schema
How do I backup GitHub issues to local Markdown files?▼

You can backup GitHub issues to local Markdown files by running dedicated scripts that synchronize issues with a specific label into a local tasks/ folder, storing one Markdown file per issue for offline access.

What is the best way to sync GitHub tasks to a local folder?▼

Syncing GitHub tasks to a local folder is best handled by deterministic scripts that pull issues from GitHub and write them as read-only Markdown backups, ensuring GitHub remains the source of truth while preserving an auditable local copy.

How do I restore Markdown files back to GitHub issues?▼

You can restore Markdown files back to GitHub issues using provided recovery workflows that migrate or convert legacy local task files from your tasks/ backup folder into new GitHub issues.

Can I edit local Markdown backups and push them back to GitHub?▼

Local Markdown backups are read-only and enforce a GitHub-first content model, meaning you must create and edit issues directly in GitHub before syncing them to your local tasks/ folder.

Does this sync workflow require any external dependencies?▼

The sync workflow runs using dedicated scripts within your repository and requires no external dependencies, relying solely on your GitHub environment and local directory structure.

Why are my local task backups not updating after editing GitHub issues?▼

Local task backups may not update because the sync scripts must be executed manually from the repository root to pull the latest changes from GitHub issues into the local tasks/ directory.

Related Skills

Explore More Product & Management Skills→
ewtwdewtwd

github-skills-publisher

Publish the local workspace skills directory to a GitHub repository.

Community
Advanced
ductrung-nguyenductrung-nguyen

fetch-github-issue

Fetch GitHub issue details by ID and save them as structured markdown files.

Community
Intermediate
NourcineAbNourcineAb

github-project-management

Automate GitHub issue tracking, board synchronization, and sprint planning workflows.

Community
Advanced
ManagedKubeManagedKube

github-issues

Create, update, fetch, and search GitHub issues via MCP tools.

Official
Intermediate