create-story

Creates minimal 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 create-story-amdmax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-story
Source: https://github.com/amdmax/claude_marketplace/tree/main/skills/create-story
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill create-story-amdmax

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 even ad-hoc changes are tracked without interrupting your development flow.

Core Features & Use Cases

  • Automated Issue Creation: Generates minimal GitHub issues with suggested titles based on staged changes.
  • Fast Path for Commits: Integrates seamlessly with commit commands when no active story is found.
  • Minimal Data Storage: Saves only essential issue details to .agile-dev-team/active-story.json for quick commit referencing.
  • Use Case: You've made a small fix and want to commit it. Instead of manually creating an issue, you run /commit, and this skill automatically suggests a title, creates the issue on GitHub, and links it to your commit.

Quick Start

Use the create-story skill to generate a new GitHub issue with a title suggested from your staged changes.

Frequently Asked Questions about create-story

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

FAQPage Schema
How do I create GitHub issues automatically from staged commits?

You can create GitHub issues automatically by running the create-story skill, which analyzes your staged commits to suggest a title and generates a minimal issue on GitHub using the CLI.

What is the best way to track ad-hoc code changes without interrupting my commit workflow?

Tracking ad-hoc changes without interrupting your workflow is best achieved by automating issue creation during the commit process, ensuring small fixes are documented on GitHub instantly without manual data entry.

Do I need the GitHub CLI installed to automate issue creation for my commits?

Yes, you need the GitHub CLI installed and properly authenticated, as the skill relies on it to create issues and handle potential network or authentication failures during your commit workflow.

How does an automated issue creator analyze staged changes to suggest issue titles?

An automated issue creator analyzes your staged changes to extract relevant context, using that information to generate a concise and relevant issue title suggestion directly within your ad-hoc commit workflow.

Where is active GitHub issue data stored for integration with commit workflows?

Active GitHub issue data is stored minimally in a local file named `.agile-dev-team/active-story.json`, allowing your commit workflow to quickly reference essential issue details without repeated API calls.