gh-issue-sync
Skill16 starsChanged 7 days agoMITView on GitHub
Manage GitHub issues locally as Markdown files. Use for triaging, searching, editing, and creating issues without leaving your editor or terminal.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- mitsuhiko/gh-issue-syncedited, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- mitsuhiko/gh-issue-sync★ 16792% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- write-ritualsSkill
- write-testsSkill
- releaseSkill
- ritualSkill
The file
Files
gh-issue-sync
Syncs GitHub issues to local Markdown files in intent/issues/open/ and intent/issues/closed/.
Commands
gh-issue-sync init # Initialize in git repo
gh-issue-sync pull # Fetch open issues (--all for closed too)
gh-issue-sync push # Push local changes (--dry-run to preview)
gh-issue-sync list # List issues (supports gh issue list flags + --search)
gh-issue-sync new "Title" # Create issue (--label, --edit)
gh-issue-sync close 42 # Close (--reason completed|not_planned)
gh-issue-sync reopen 42
gh-issue-sync status # Show local changes
gh-issue-sync diff 42 # Show diff (--remote to re-fetch)File Format
intent/issues/open/42-fix-login-bug.md:
---
title: Fix login bug
labels: [bug, priority:high]
assignees: [alice]
milestone: v1.0
state: open
# For closed: state_reason: completed|not_planned
# Optional: parent: 10, blocked_by: [11, 12], blocks: [15]
---
Issue body in Markdown.Issue number is derived from the filename, not stored in frontmatter.
Temporary Issues
New issues get a T-prefixed ID (e.g., T1a2b3c). The filename must start with T:
intent/issues/open/T1a2b3c-my-new-issue.mdOn push, the file is renamed to the real issue number (e.g., 42-my-new-issue.md) and number: in frontmatter is updated. Any #T1a2b3c references in other issues are also updated to #42.
Comments
To post a comment when pushing, create a .comment.md file next to the issue:
intent/issues/open/42.comment.md
intent/issues/open/42-fix-login-bug.comment.mdContent is plain Markdown. The file is deleted after the comment is posted.
Notes
- Pull skips conflicts; use
--forceto overwrite local
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

