ghs-backlog-sync

Synchronize local health backlog items to GitHub Issues via gh CLI.

2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-backlog-sync
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ghs-backlog-sync
Source: https://github.com/Atypical-Consulting/GitHubSkills/tree/main/.claude/skills/ghs-backlog-sync
Command: npx skills add https://github.com/Atypical-Consulting/GitHubSkills --skill ghs-backlog-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill bridges the gap between local repository health findings and actionable GitHub Issues, ensuring that important issues are tracked and visible to the team.

Core Features & Use Cases

  • Automated Issue Creation: Creates GitHub Issues for failing health checks.
  • Status Synchronization: Updates existing issues, closing them when checks pass or reopening them if they fail again.
  • Metadata Management: Adds and updates sync information (Issue number, URL) in local backlog files.
  • Use Case: After running a repository scan, use this Skill to automatically create GitHub Issues for all critical failures, ensuring developers are aware and can prioritize fixes.

Quick Start

Use the ghs-backlog-sync skill to sync local health backlog items to GitHub Issues for the current repository.

Frequently Asked Questions about ghs-backlog-sync

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

FAQPage Schema
How do I sync local repository health backlog items to GitHub Issues?

To sync backlog items to GitHub Issues, use this Skill to create new issues for health check failures, update existing ones, and close resolved items automatically. It requires the gh CLI for GitHub API interactions.

Do I need the gh CLI to automate GitHub Issue creation from a repository scan?

Yes, the gh CLI is required for GitHub Issue creation and status synchronization. This Skill uses the gh CLI to interact with the GitHub API, ensuring backlog findings are tracked as issues.

What happens to existing GitHub Issues when a repository health check passes or fails again?

When health checks pass or fail again, this Skill performs status synchronization by closing resolved GitHub Issues or reopening them if failures recur. It ensures repository health findings remain accurately tracked.

Can I update local backlog files with GitHub Issue metadata automatically?

Yes, this Skill provides metadata management by adding and updating sync information, such as the Issue number and URL, directly in local backlog files. This links local repository health findings to GitHub Issues.

What is the best way to track repository health findings in GitHub?

The best way to track repository health findings is by synchronizing local backlog items to GitHub Issues. This Skill automates issue creation and status updates, ensuring developers can prioritize fixes directly within GitHub.

Does this backlog sync approach work with existing repository health check formats?

This Skill adheres to specific sync and backlog formats to ensure local repository health findings map correctly to GitHub Issues. It synchronizes failures, updates existing issues, and closes resolved items based on those formats.