maiconfz--github-interactive-issue-implementation-planner--github-issue-intake

Fetches GitHub issue context via gh CLI and emits a structured issue brief.

3|1|Updated May 2, 2026
One-click install
npx skills add https://github.com/agents-repo/registry --skill maiconfz-github-interactive-issue-implementation-planner-github-issue-intake-agents-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maiconfz--github-interactive-issue-implementation-planner--github-issue-intake
Source: https://github.com/agents-repo/registry/tree/main/.cursor/skills/maiconfz/github-interactive-issue-implementation-planner/maiconfz--github-interactive-issue-implementation-planner--github-issue-intake
Command: npx skills add https://github.com/agents-repo/registry --skill maiconfz-github-interactive-issue-implementation-planner-github-issue-intake-agents-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation planning from a GitHub issue requires manually collecting the issue title, body, labels, comments, and repository context. This Skill automates that intake by resolving an issue number or URL, verifying it is an issue rather than a pull request, and producing a canonical issue brief for downstream planning agents. ## Core Features & Use Cases - Issue Reference Resolution: Parses a bare issue number or full GitHub issue URL and resolves the target repository from the URL, the gh CLI, or the git origin remote, asking the user when ambiguous. - Issue Verification and Fetching: Confirms the reference is an issue (not a pull request) via the GitHub API, then fetches title, body, state, labels, author, assignees, milestone, and comments using gh. - Structured Issue Brief: Summarizes the comment thread, surfaces acceptance criteria and validation commands, and outputs a canonical issue-brief object with a fetchedAt timestamp and linked references. - Use Case: A developer pastes a GitHub issue URL to begin planning an implementation; the Skill fetches the full issue and discussion context and hands a structured brief to downstream planner agents without them calling gh again. ## Quick Start Resolve GitHub issue number 42 in this repository and produce a structured issue brief for implementation planning.

Frequently Asked Questions about maiconfz--github-interactive-issue-implementation-planner--github-issue-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch a GitHub issue and its comments with the gh CLI?▼

Use gh issue view with the issue number and repository to retrieve fields like title, body, state, labels, author, and assignees as JSON, and add the --comments flag to include the discussion thread. This Skill wraps those commands into a single intake step that outputs a structured issue brief.

How to check if a GitHub reference is an issue or a pull request?▼

Query the GitHub API with gh api repos/owner/name/issues/<n> and check whether the pull_request field is present. If it is a pull request, this Skill stops and asks for a real issue number or URL instead of proceeding.

Can I use a full GitHub issue URL instead of an issue number?▼

Yes, the Skill accepts either a bare issue number or a full GitHub issue URL. When a URL is provided, the repository owner and name are parsed directly from it; otherwise the repository is inferred from gh repo view or the git origin remote.

What happens if the repository cannot be determined automatically?▼

If the repository cannot be resolved from the issue URL, gh repo view, or the git origin remote, the Skill asks the user structured clarifying questions rather than guessing. You can also pass an explicit repository in owner/name form to skip inference.

Does this Skill write code or create pull requests from the issue?▼

No, it only performs remote intake: fetching and structuring issue context into an issue brief. It explicitly does not draft implementation steps, edit files, commit, push, or open pull requests; those tasks belong to downstream planner agents.