Gh Issue View
- 5 installs
- 1 repo stars
- Updated July 11, 2026
- juparave/dotfiles
Helps with ai & agent building tasks.
About
gh-issue-view is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.
- gh-issue-view
- AI & Agent Building
- AI-coding skill
Gh Issue View by the numbers
- 5 all-time installs (skills.sh)
- Ranked #13,046 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/juparave/dotfiles --skill gh-issue-viewAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 5 |
|---|---|
| repo stars | ★ 1 |
| Last updated | July 11, 2026 |
| Repository | juparave/dotfiles ↗ |
What it does
Helps with ai & agent building tasks.
Files
GitHub Issue / PR Viewer
The Problem
Running gh issue view <number> or gh pr view <number> without --json triggers a GraphQL error about the deprecated projectCards field (classic Projects sunset), causing exit code 1 even when the issue data is perfectly accessible. This breaks silently and wastes retries.
Always Use This Pattern
When reading an issue:
gh issue view <number> --json title,body,state,labels,assignees,comments,number,url,author,createdAt,updatedAtWhen reading a PR:
gh pr view <number> --json title,body,state,labels,assignees,comments,number,url,author,createdAt,updatedAt,mergeable,mergeStateStatus,headRefName,baseRefName,reviewsNever use bare gh issue view <number> or gh pr view <number> without --json — they will fail.
Repo Detection
If not already in a git repo with a GitHub remote, or if the user specifies a repo:
gh issue view <number> --repo owner/repo --json title,body,state,...To auto-detect the current repo:
gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/nullIf auto-detect fails (not a GitHub repo), ask the user for owner/repo.
Presenting the Output
After fetching, present:
- Title and #number (with URL as a link)
- State (open/closed) and Labels
- Author and Created date
- Body — render as markdown
- Comments — show each with author + timestamp + body; collapse threads longer than 5 comments and offer to expand
Don't dump raw JSON at the user — parse and display it clearly.
Listing Issues / PRs
For listing, same rule applies — avoid fields that touch projectCards:
gh issue list --json number,title,state,labels,assignees,author,createdAt,url
gh pr list --json number,title,state,labels,assignees,author,createdAt,url,headRefName,baseRefNameRelated skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10