How do I install the Gh Issue View skill?

Run npx skillmds@latest add juparave/gh-issue-view in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Issue View safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Issue View?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Issue View free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Issue View?

juparave (@juparave) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Issue View by juparave — Agent Skill

Name: Gh Issue View
Rating: 4.2 (5 reviews)
Author: juparave

File contents

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,updatedAt

When reading a PR:

gh pr view <number> --json title,body,state,labels,assignees,comments,number,url,author,createdAt,updatedAt,mergeable,mergeStateStatus,headRefName,baseRefName,reviews

Never 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/null

If 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,baseRefName

---name: gh-issue-viewdescription: Read GitHub issues and PRs using the gh CLI. Use this skill whenever the user asks to read, view, check, or look at a GitHub issue or pull request — even if they just say "look at issue 18" or "what does---# GitHub Issue / PR Viewer## The ProblemRunning `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 PatternWhen reading an issue:```bashgh issue view <number> --json title,body,state,labels,assignees,comments,number,url,author,createdAt,updatedAt```When reading a PR:```bashgh pr view <number> --json title,body,state,labels,assignees,comments,number,url,author,createdAt,updatedAt,mergeable,mergeStateStatus,headRefName,baseRefName,reviews```**Never** use bare `gh issue view <number>` or `gh pr view <number>` without `--json` — they will fail.## Repo DetectionIf not already in a git repo with a GitHub remote, or if the user specifies a repo:```bashgh issue view <number> --repo owner/repo --json title,body,state,...```To auto-detect the current repo:```bashgh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null```If auto-detect fails (not a GitHub repo), ask the user for `owner/repo`.## Presenting the OutputAfter 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 expandDon't dump raw JSON at the user — parse and display it clearly.## Listing Issues / PRsFor listing, same rule applies — avoid fields that touch projectCards:```bashgh issue list --json number,title,state,labels,assignees,author,createdAt,urlgh pr list --json number,title,state,labels,assignees,author,createdAt,url,headRefName,baseRefName```

Frequently asked questions

Gh Issue View