Read the GitHub plan issue given as argument. Use when the user tells you to "read this github plan issue" with the issue as argument.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add gjoranv/claude-plan-skills --skill gh-read-plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Gh Read Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gjoranv-gh-read-plan)More formats (shields.io, HTML) on the badges page.
---
name: gh-read-plan
description: Read the GitHub plan issue given as argument. Use when the user tells you to "read this github plan issue" with the issue as argument.
argument-hint: "[owner/repo#number]"
allowed-tools: Bash
---
Read the GitHub issue in $ARGUMENTS (issue URL or `owner/repo#number`) containing the detailed plan for the work that will be started or continued in this conversation.
When reading the issue, check both the body and comments for content. Steps may be in a separate **Steps** comment (new format) or in the issue body (old format). Check for:
* a list of steps (with checkboxes) -- in the body or a Steps comment
* a design section -- in the body or a Design comment
* a diagram -- in the body or a Diagram comment
* links to relevant documentation, code, resources, and related issues
* a list of prerequisites, and if so, ask the user if those have been completed
* a link to one or more pull requests -- if so, read their diffs to understand what has already been implemented
Try to verify, from the comments and pull requests, which steps have been completed, and which are still pending.
If a durable-memory CLI is configured, query it with the issue's distinctive terms after reading. See the memory tool's own integration doc for mechanics.
Tell the user what you have learned from reading the issue, and ask any clarifying questions you may have about the work to be done.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
