Skip to content

serejaris/personal-corp-os / skills/gh-issues

gh-issues

Verified

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.

FileKindSize
SKILL.mdskill md7.1 KB
assets/illustration.pngbinary488.2 KB
references/context-template.mdmarkdown2.1 KB

references/context-template.md

View on GitHub
# AI Context Template

Use this template for storing session context in GitHub issues.

## Full Template

```markdown
<!-- AI-CONTEXT:START -->
## AI Session Context
_Last updated: YYYY-MM-DD HH:MM_

### Status
**IN_PROGRESS** | **DONE** | **BLOCKED**

### Progress
- [x] Completed item
- [ ] Pending item

### Key Files
- `path/file.ts:45-78` — description
- `path/other.ts:120` — description

### Decisions
- **Decision**: Reasoning/WHY

### Blockers
_None_ or list blockers

### Next Steps
1. First action
2. Second action

### Resume Context
Brief summary for quick pickup by next session.
<!-- AI-CONTEXT:END -->
```

## Minimal Template

For quick context saves:

```markdown
<!-- 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 -->
```

## Example: Real Context

```markdown
<!-- AI-CONTEXT:START -->
## AI Session Context
_Last updated: 2026-01-07 15:30_

### Status
**IN_PROGRESS**

### Progress
- [x] Analyzed current bot flow
- [x] Reviewed reference implementation
- [ ] Create simplified flow diagram
- [ ] Implement changes

### Key Files
- `handlers/start.py:45-78` — current start handler
- `data/config.yaml` — configuration
- `handlers/payment.py:120` — payment flow

### Decisions
- **Remove intermediate steps**: Go directly to payment after selection (reduces friction)
- **Reference**: Competitor's 3-step flow is ideal

### Blockers
_None_

### Next Steps
1. Draw new flow diagram
2. Simplify handlers/start.py
3. Test with staging

### Resume Context
Task: simplify flow, restore conversions.
Reference: competitor's simple flow.
Done: analysis of current state.
Next: create new flow diagram.
<!-- AI-CONTEXT:END -->
```

## Tips

| Section | Purpose |
|---------|---------|
| Status | Quick visual scan — IN_PROGRESS/DONE/BLOCKED |
| Progress | Checklist of tasks |
| Key Files | `file:line` format for quick navigation |
| Decisions | WHY not WHAT — reasoning matters |
| Blockers | What's stopping progress |
| Next Steps | Concrete actions |
| Resume Context | Cold start summary — minimum to continue |
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall