skills.rest
lsst-sqre
lsst-sqreOFFICIAL
Explore all skills by this author →
WebsiteGitHub

github-issues

Synchronize GitHub issues with local .issues directory plans using gh CLI workflows.

2|1|Updated Jan 7, 2021
Search Tags:#planning#synchronization#issues#project-management#gh-cli#github-issues#local-first
One-click install
npx skills add https://github.com/lsst-sqre/squareone --skill github-issues-lsst-sqre
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issues
Source: https://github.com/lsst-sqre/squareone/tree/main/.claude/skills/github-issues
Command: npx skills add https://github.com/lsst-sqre/squareone --skill github-issues-lsst-sqre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables local-first planning and synchronization of GitHub issues. Create issue plans in a dedicated .issues/ directory, define multi-phase projects, and synchronize with GitHub using gh and git workflows.

Core Features & Use Cases

  • Local issue planning: Create and organize issues offline before syncing.
  • Multi-phase projects: Define parent issues with sub-issues for sequential work.
  • GitHub synchronization: Push and pull plans to/from GitHub using gh CLI.

Quick Start

Create a simple plan in .issues/2025-01-user-auth.md with initial research and proposed design, then plan to sync using /sync-issue.

Frequently Asked Questions about github-issues

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

FAQPage Schema
How do I plan and sync GitHub issues locally before pushing to GitHub?▼

Local-first planning uses a .issues/ directory where you create markdown files with frontmatter schema, define multi-phase projects with parent and sub-issues, then sync to GitHub using /sync-issue and gh CLI integration.

Can I organize issues with sub-issues and phases in a local workflow?▼

Yes. The Skill supports multi-phase issue structures with parent issues and sub-issues defined in .issues/ markdown files, enabling sequential project planning before synchronization.

What file format does the .issues directory use for issue plans?▼

Issue plans use markdown files with a defined frontmatter schema stored in the .issues/ directory, supporting both single and multi-phase issue structures for GitHub synchronization.

How do I keep local issue plans synchronized with GitHub?▼

Use /sync-issue to push local plans to GitHub and pull updates back. The Skill integrates gh CLI and git workflows to map local .issues/ plans bidirectionally with GitHub issues.

Do I need to use the command line to manage local GitHub issues?▼

Yes. The Skill provides commands like /plan-issue, /update-issue, /sync-issue, and /list-issues that work with gh CLI and git workflows to manage the .issues/ directory structure.

What's the best way to structure a multi-phase project in local issue files?▼

Define parent issues with sub-issues in separate markdown files within .issues/, each with frontmatter metadata, enabling hierarchical project organization that syncs to GitHub's issue structure.

Related Skills

Explore More Software Engineering Skills→
zachmayerzachmayer
2

private-repo

Automates initialization and remote sync of local directories to private GitHub repositories.

Community
Intermediate
BrennonTWilliamsBrennonTWilliams
7

ll-sync-issues

Synchronize local development issues with GitHub Issues via the GitHub API.

Community
Intermediate
Ven0m0Ven0m0
6

pr-creator

Create GitHub pull requests with branch management and preflight checks.

Community
Intermediate
blackplume233blackplume233
12

issue-manager

Manage GitHub Issues through an Obsidian-compatible local cache with YAML frontmatter and Wikilinks.

Community
Advanced