github:story-create

Create GitHub issues from staged changes using the GitHub CLI.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill github-story-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github:story-create
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/github%3Astory-create
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill github-story-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yq, jq, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating GitHub issues directly from your commit workflow, ensuring that every piece of work is tracked without manual intervention.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues based on staged changes, suggesting titles and bodies.
  • Minimal Data Storage: Saves only essential issue details to .claude/active-story.json for quick commit integration.
  • Use Case: When you stage changes for a bug fix, running /commit will automatically trigger this skill to create a new GitHub issue, assign it a title based on your changes, and link it to your commit.

Quick Start

Use the github:story-create skill to create a new GitHub issue with the title "Implement user authentication".

Frequently Asked Questions about github:story-create

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

FAQPage Schema
How do I automate GitHub issue creation from staged git changes?

Yes, you can automate GitHub issue creation directly from your commit workflow. The skill analyzes staged git changes to suggest issue titles and optionally generates bodies from git diff, saving essential data to a local JSON file for seamless integration.

Do I need the GitHub CLI installed to create issues from commit workflows?

Yes, you need the GitHub CLI installed to create issues from commit workflows. The skill depends on the gh command-line tool, alongside yq and jq, to analyze git diff data and manage the local JSON file storing issue details.

What's the best way to link GitHub issues to my commit workflow?

Link GitHub issues to your commit workflow by saving essential issue details to a local JSON file. When you stage changes, the skill creates the issue and stores its data locally, ensuring seamless integration with your subsequent commit operations.

How does git diff analysis work for generating GitHub issue bodies?

Git diff analysis generates GitHub issue bodies by examining your staged changes to automatically suggest relevant content. The skill uses this diff analysis to optionally populate the issue body, ensuring the created issue accurately reflects the code modifications.

Can I use this automated issue creation for tracking bug fixes in git?

Yes, you can use automated issue creation for tracking bug fixes in git. When you stage changes for a bug fix, the skill automatically creates a new GitHub issue, assigns a title based on your changes, and links it to your commit.

Why does my commit workflow need a local JSON file for issue tracking?

Your commit workflow needs a local JSON file for issue tracking to store essential issue data for quick integration. By saving minimal issue details locally, the skill ensures seamless linking between the created GitHub issue and your subsequent commit operations.