skills.rest
norrietaylor
norrietaylorCOMMUNITY
Explore all skills by this author →
GitHub

gh-sync

Starts a background sync of GitHub issues and PRs into the knowledge base.

24|9|Updated Mar 22, 2026
Search Tags:#github#issues#status#deduplication#pull-requests#knowledge-base#background-processing
One-click install
npx skills add https://github.com/norrietaylor/distillery --skill gh-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-sync
Source: https://github.com/norrietaylor/distillery/tree/main/skills/gh-sync
Command: npx skills add https://github.com/norrietaylor/distillery --skill gh-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub issues and pull requests often live in isolation, making it hard to search, relate, and preserve decisions across projects. gh-sync bridges GitHub activity to Distillery's knowledge base, creating searchable, linkable entries that preserve provenance.

Core Features & Use Cases

  • Start a background sync for a repository and receive a job_id to monitor progress.
  • Retrieve progress for a single job or list recent jobs with status details.
  • Ensure issues and PRs are deduplicated and properly wired to cross-reference entries in the knowledge base.
  • Use cases include capturing decisions from issues/PRs for traceability and surfacing context alongside session notes.

Quick Start

Start a background GitHub sync for a repository by saying gh-sync owner/repo, then check progress with /gh-sync status <job_id>.

Frequently Asked Questions about gh-sync

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

FAQPage Schema
How do I sync GitHub issues and pull requests into a searchable knowledge base?▼

You can sync GitHub issues and pull requests into a searchable knowledge base by initiating a background process for a repository. This fetches, deduplicates, and links entries to preserve provenance and cross-reference context.

How do I monitor the progress of a GitHub repository sync?▼

To monitor a GitHub repository sync, use the job_id returned when the background sync starts. You can check the progress of a single job or list recent jobs to retrieve current status details.

How does deduplication work when synchronizing GitHub issues?▼

Deduplication during GitHub issue synchronization ensures that identical issues and pull requests are not imported multiple times. The backend handles fetching and processing to properly wire cross-reference entries.

Why sync GitHub issues into a knowledge base instead of leaving them in the repository?▼

Syncing GitHub issues into a knowledge base prevents decisions from living in isolation. It creates searchable, linkable entries that capture project context and surface traceability alongside session notes.

Do I need any external dependencies to start syncing GitHub pull requests?▼

No external dependencies are required to start syncing GitHub pull requests. The skill initiates the background sync directly and the backend MCP server handles the fetching and linking automatically.

Related Skills

Explore More Software Engineering Skills→
roborev-devroborev-dev
1.6k

roborev:address

Fetch a roborev review by job_id and implement its fixes.

Official
Advanced
mattwoodcomattwoodco
3

queue

Implement a serverless background job queue with Inngest and PostgreSQL.

Community
Advanced
hve4638hve4638

wiki

Store and retrieve persistent project knowledge in a markdown wiki.

Community
Advanced
devopstalesdevopstales
1

engram-backlog-triage

Classify and prioritize GitHub issues and pull requests via the GitHub API.

Community
Advanced