Menu
View a GitHub/Gitea issue by number, URL, or search query
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate a single-file HTML artifact (status report, slide deck, prototype, throwaway editor, flowchart, etc.) and open it in the browser. Use when the user wants a one-off visual artifact instead of markdown — for sharing, reference, or interactive exploration.
Gather context from the codebase and (optionally) the web, then propose multiple ways to move forward with tradeoffs, relative impact, and effort. Use when user wants to explore options, weigh approaches, or asks "what are my options" / "how should I tackle this" before committing to a plan.
Propose a concrete plan to cut a branch and implement a change as one or more atomic commits, grounded in the current codebase and (optionally) outside research. Use when user wants a step-by-step implementation plan, asks "propose a plan" / "how would you implement this", or is ready to move from discussion to execution.
Summarize what shipped over a date range, commit range, or release tag — synthesizes git log, GitHub PRs, and Linear issues into a single markdown brief.
View a Sentry issue by short ID (e.g. PROJECT-123) or URL. Shows details, status, latest event, and tag distribution. Use when user wants to view, check, or look up a Sentry issue, error, or event.
Break a PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a PRD to issues, create implementation tickets, or break down a PRD into work items.
| name | view-issue |
| description | View a GitHub/Gitea issue by number, URL, or search query |
| argument-hint | <issue-number, URL, or search query> |
| allowed-tools | Bash(gh issue *), mcp__gitea__issue_read, mcp__gitea__list_issues |
git remote -vgit branch --show-currentCheck the git remotes above to determine the platform:
github.com → use gh CLIView and summarize the issue.
If $ARGUMENTS is a number, view that issue:
gh issue view $ARGUMENTS
gh issue view --comments $ARGUMENTS
If $ARGUMENTS is a URL, extract the issue number and view it:
gh issue view <number> --repo <owner/repo>
gh issue view --comments <number> --repo <owner/repo>
If $ARGUMENTS is text (not a number or URL), search for matching issues:
gh issue list --search "$ARGUMENTS"
Then let the user pick one, or if there's a single match, view it directly.
If no $ARGUMENTS is provided, list recent open issues:
gh issue list --limit 10
Extract owner/repo from the remote URL. If $ARGUMENTS is a number, use it as the index. Otherwise, use mcp__gitea__list_issues to find matching issues, then:
mcp__gitea__issue_read with method get for detailsmcp__gitea__issue_read with method get_comments for commentsSummarize concisely: title, state, author, assignees, labels, a brief description, and any notable comments.