/gh-issues
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:
$ npx -y skills add serejaris/personal-corp-os --skill gh-issues --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/gh-issues
Context preview
The summary Claude sees to decide when to auto-load this skill.
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:
SKILL.md
gh-issues.SKILL.mdname: gh-issues
description: >-
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.
GitHub Issues CLI
Efficient GitHub Issues management via `gh` CLI with AI session context storage.
Table of Contents
1. [Quick Reference](#quick-reference) 2. [JSON Output](#json-output-patterns) 3. [Search Filters](#advanced-search-filters) 4. [Bulk Operations](#bulk-operations) 5. [Issue to PR Workflow](#issue-to-pr-workflow) 6. [Milestones](#milestones-via-api) 7. [AI Session Context](#ai-session-context) 8. [Task Workflow](#task-workflow) 9. [Examples](#examples) 10. [Common Mistakes](#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 merged
Milestones 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
1. **Start work** — load context from issue 2. **Work on task** — track progress mentally 3. **Pause/Stop** — save context to issue comment 4. **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...Read more
name: gh-issues description: >- 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.
GitHub Issues CLI
Efficient GitHub Issues management via `gh` CLI with AI session context storage.
Table of Contents
1. [Quick Reference](#quick-reference) 2. [JSON Output](#json-output-patterns) 3. [Search Filters](#advanced-search-filters) 4. [Bulk Operations](#bulk-operations) 5. [Issue to PR Workflow](#issue-to-pr-workflow) 6. [Milestones](#milestones-via-api) 7. [AI Session Context](#ai-session-context) 8. [Task Workflow](#task-workflow) 9. [Examples](#examples) 10. [Common Mistakes](#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 merged
Milestones 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
1. **Start work** — load context from issue 2. **Work on task** — track progress mentally 3. **Pause/Stop** — save context to issue comment 4. **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...Personal Corp is a way to run a one-person company through AI agents: tasks out of your head, departments instead of one person's memory, a weekly retro instead of "I'll sort it out someday".
Other skills on personal-corp-os.
- /paperclip-api
Use when managing Paperclip AI agent companies - creating tasks, managing agents, approving hires, running heartbeats, or any Paperclip control-plane operations via CLI or REST API. Triggers on "paperclip", "задача агенту", "одобри найм", "heartbeat", "запусти агента".
Open skill - /art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
Open skill - /cc-analytics
Use when user asks for Claude Code usage stats, weekly analytics, project activity summary, or wants to see what projects were worked on. Triggers on "аналитика", "статистика claude", "cc stats", "weekly report", "что делал
Open skill - /ceo-council
Use when needing strategic project analysis from multiple independent expert perspectives. Triggers on business decisions, growth strategy, product direction, competitive analysis, or any situation where diverse C-level opinions reduce blind spots
Open skill - /claude-md-writer
Use when creating or refactoring CLAUDE.md files - enforces best practices for size, structure, and content organization
Open skill - /corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp-* owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур",
Open skill

