gh-issues
Skill243 starsChanged 3 months agoMITView on GitHub
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq, search filters, issue-to-PR workflow, AI session context storage, task workflow with labels.
- Commits and pushes
35 other projects use a version of this.
Adopted by
Most recently taken up by
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- QVerisAI/QVerisBottheir own version, first seen Nov 1, 2026
- lelborn/skillstheir own version, first seen Nov 1, 2026
- newkirkjosh/skillstheir own version, first seen Nov 1, 2026
- OpenClawAndroid/openclaw-android-assistanttheir own version, first seen Oct 17, 2026
- HybridAIOne/hybridclawtheir own version, first seen Oct 13, 2026
Used with
Projects with it also use discord-e2e, openclaw-repair-sweep and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
clawdbotSkillplugin-sdk-impact
Count Plugin SDK consumers across live ClawHub releases and bundled OpenClaw plugins before deprecation, removal, or behavior changes; supports public release-date filters.
Also in 7 projects that use this
AtomicBot-aiSkilltaskflow-inbox-triage
Also in 6 projects that use this
hkyutongSkillnode-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.
Also in 18 projects that use this
- +2 more from molt-bot
Other versions35 projects use a version of this.
Word for word · 1
- serejaris/personal-corp-os★ 243100% same
Edited · 0
None found.
Wrote their own version · 34
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- openclaw/openclaw★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- spinabot/brigade★ 11ksame name
- the-open-agent/openagent★ 5.7ksame name
- casibase/casibase★ 5.7ksame name
24 more not listed
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 repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- art-directorSkill
- audit-agent-rulesSkill
- avatarSkill
- benchmarkSkill
- cc-analyticsSkill
- ceo-councilSkill
- claude-md-writerSkill
- claude-sessions-syncSkill
- corp-doctorSkill
- corp-newSkill
- dailySkill
- fable-ruki-agentySkill
- grill-meSkill
- harnessSkill
- html-draftSkill
- ideaSkill
- it-ram-doctorSkill
- make-3dSkill
- make-landingSkill
- managerSkill
- meeting-copilotSkill
- readme-generatorSkill
- retroSkill
- safe-public-releaseSkill
- sdlc-milestonesSkill
- tg-bot-opsSkill
- to-issuesSkill
- to-prdSkill
- weekly-planningSkill
- weekly-retroSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 34 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 45
Always use --json for parsing.
“Common” is measured: kept by at least 6 in 10 of the 34 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
GitHub Issues CLI
Efficient GitHub Issues management via gh CLI with AI session context storage.
Table of Contents
- Quick Reference
- JSON Output
- Search Filters
- Bulk Operations
- Issue to PR Workflow
- Milestones
- AI Session Context
- Task Workflow
- Examples
- Common Mistakes
Quick Reference
| Task | Command |
| Create issue | gh issue create -t "Title" -b "Body" -l bug -a @me |
| Active tasks | gh issue list -l in-progress -s open |
| List open bugs | gh issue list -l bug -s open |
| View as JSON | gh issue view 123 --json number,title,body,labels,state |
| Close with comment | gh issue close 123 -c "Fixed in #456" |
| Edit labels | gh issue edit 123 --add-label priority:high |
| Start work | gh issue edit 45 --add-label in-progress |
| Create branch | gh issue develop 123 --checkout |
| Load context | gh issue view 45 --json comments --jq '.comments[] | select(.body | contains("AI-CONTEXT"))' |
JSON Output Patterns
Always use --json for parsing. Fields: number, title, body, state, labels, assignees, milestone, author, createdAt, updatedAt, comments, url.
gh issue view 123 --json number,title,labels,state
gh issue list --json number,title,labels --jq '.[] | select(.labels[].name == "bug")'
gh issue list -l bug --json number --jq '.[].number'Advanced Search Filters
gh issue list --search "is:open author:username"
gh issue list --search "created:>=2026-01-01 created:<=2026-01-07"
gh issue list --search "label:bug label:priority:high"
gh issue list --search "is:open -label:wontfix"
gh issue list --search "milestone:v2.0"Bulk Operations
gh issue edit 10 15 20 --add-label "priority:high"
gh issue close 10 15 20 -c "Duplicate of #5"
gh issue list -l needs-triage --json number --jq '.[].number' | \
xargs -I{} gh issue edit {} --add-label reviewedIssue to PR Workflow
gh issue develop 123 --checkout # Create branch from issue
git add . && git commit -m "fix: #123" # Commit with reference
gh pr create --fill # Create PR (auto-links)
gh issue close 123 -c "Fixed in PR #456" # Close when mergedMilestones via API
gh api repos/:owner/:repo/milestones --jq '.[].title'
gh issue edit 123 -m "v2.0"AI Session Context
Store session context in GitHub issues for seamless task handoff.
Read Context
# Get AI context from issue comments
gh issue view 45 --json comments --jq '
.comments[] | select(.body | contains("AI-CONTEXT:START")) | .body
'
# Get comment ID for updates
gh issue view 45 --json comments --jq '
.comments[] | select(.body | contains("AI-CONTEXT:START")) | .id
'Save Context
# Create new context comment
gh issue comment 45 --body-file .ai-context.md
# Update existing (replace COMMENT_ID)
gh api repos/:owner/:repo/issues/comments/COMMENT_ID \
--method PATCH -f body="$(cat .ai-context.md)"Context Template
See references/context-template.md for full template. Minimal version:
<!-- AI-CONTEXT:START -->
## Context | IN_PROGRESS
**Files:** `file.py:45`, `other.py:120`
**Done:** task1, task2
**Next:** next task
**Resume:** One-line summary for cold start
<!-- AI-CONTEXT:END -->Workflow
- Start work — load context from issue
- Work on task — track progress mentally
- Pause/Stop — save context to issue comment
- Resume later — load context, continue
Task Workflow
Manage issue lifecycle with labels.
Labels
| Label | Meaning |
backlog | In queue |
in-progress | Active work |
blocked | Blocked |
review | Needs review |
View Active Tasks
# My active issues
gh issue list -l in-progress -s open
# All my assigned issues
gh issue list --assignee @me -s open
# Issues with context
gh issue list -s open --json number,title,labels --jq '
.[] | select(.labels[].name == "in-progress") | "#\(.number): \(.title)"
'Start Working
# Mark as in-progress
gh issue edit 45 --add-label in-progress --remove-label backlog
# View issue + load context
gh issue view 45 --json number,title,body,comments --jq '{
number, title, body,
context: (.comments[] | select(.body | contains("AI-CONTEXT")) | .body) // "No context"
}'Pause/Block
# Mark as blocked
gh issue edit 45 --add-label blocked --remove-label in-progress
# Add blocking comment
gh issue comment 45 --body "Blocked: waiting for API access"Complete
# Close with comment
gh issue close 45 -c "Done in commit abc123"
# Or close via PR (auto-closes if PR body contains "Fixes #45")Examples
Create Issue for Task
gh issue create -t "Simplify bot flow" -b "## Problem
Bot stopped converting. Current flow is complex.
## Reference
Simple flow example from competitor.
## Tasks
- [ ] Analyze current flow
- [ ] Create new diagram
- [ ] Implement"Start Working on Issue
# 1. View issue with context
gh issue view 45 --json number,title,body,comments --jq '{
number, title, body,
context: (.comments[] | select(.body | contains("AI-CONTEXT")) | .body) // "No context"
}'
# 2. Create branch
gh issue develop 45 --checkout
# 3. Work...Save Progress Before Stopping
# Create context file
cat > .ai-context.md << 'EOF'
<!-- AI-CONTEXT:START -->
## AI Session Context
_Last updated: 2026-01-07 16:00_
### Status
**IN_PROGRESS**
### Progress
- [x] Analyzed current flow
- [ ] Create new diagram
### Key Files
- `handlers/start.py:45-78` — start handler
- `data/courses.yaml` — config
### Next Steps
1. Draw simplified flow
2. Implement changes
### Resume Context
Simplifying bot flow. Analyzed current state. Next: create diagram.
<!-- AI-CONTEXT:END -->
EOF
# Save to issue
gh issue comment 45 --body-file .ai-context.mdResume Work
# Load context
CONTEXT=$(gh issue view 45 --json comments --jq '
.comments[] | select(.body | contains("AI-CONTEXT")) | .body
' 2>/dev/null)
echo "$CONTEXT"
# Continue from where you left off...Common Mistakes
| Mistake | Fix |
Missing --json | Always --json field1,field2 |
| Loop instead of multi-arg | gh issue edit 1 2 3 |
Using grep on output | Use --jq |
Forgot -s all for closed | Default is open only |
{owner}/{repo} in API | Use :owner/:repo |
| Duplicate context comments | Update existing, don't create new |
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.

