create-issue-from-issue-number

Re-analyzes GitHub Issues and updates implementation plans based on latest code state.

4|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/getty104/claude-task-worker --skill create-issue-from-issue-number
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue-from-issue-number
Source: https://github.com/getty104/claude-task-worker/tree/main/plugin/skills/create-issue-from-issue-number
Command: npx skills add https://github.com/getty104/claude-task-worker --skill create-issue-from-issue-number

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, claude-code, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill re-analyzes existing GitHub Issues, refreshing the implementation plan against the latest code state, ensuring that Issue details are up-to-date with the current codebase.

Core Features & Use Cases

  • Issue Re-analysis: Re-analyze Issue title and body to refresh implementation plans.
  • Code State Sync: Sync Issue details with the latest code state for accuracy.
  • Use Case: Ideal for when an Issue needs to be re-evaluated after new code changes or updates.

Quick Start

Run the skill with the Issue number to re-analyze and update the Issue details: /create-issue-from-issue-number <Issue number>

Frequently Asked Questions about create-issue-from-issue-number

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

FAQPage Schema
How do I update a GitHub Issue implementation plan to reflect recent code changes?

To update a GitHub Issue implementation plan after recent code changes, you can re-analyze the Issue against the latest codebase state. This process refreshes the Issue details and implementation plan to ensure accuracy with the current code.

Why should I re-analyze GitHub Issues against the latest code state?

Re-analyzing GitHub Issues against the latest code state ensures that your implementation plans remain accurate and up-to-date. This prevents development drift by syncing Issue details with the current codebase after new updates or changes.

Does the GitHub Issue re-analysis tool require Claude Code and GitHub API access?

Yes, executing the GitHub Issue re-analysis requires access to the GitHub API and the Claude Code plugin. These dependencies are necessary to fetch Issue details and sync them with the current code state.

What's the best way to refresh implementation plans for outdated GitHub Issues?

The best way to refresh implementation plans for outdated GitHub Issues is to use a re-analysis tool that syncs Issue details with the latest code state. This approach evaluates the Issue title and body against recent codebase updates.

How do I re-evaluate an existing GitHub Issue after merging new code?

To re-evaluate an existing GitHub Issue after merging new code, run the re-analysis command with the specific Issue number. This action updates the Issue details and implementation plan based on the latest code state.