create-issue

Create GitHub issues from uncommitted changes or commits and update CHANGELOG.

9.9k|1.8k|Updated Aug 8, 2016
One-click install
npx skills add https://github.com/gitkraken/vscode-gitlens --skill create-issue-gitkraken
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-issue
Source: https://github.com/gitkraken/vscode-gitlens/tree/main/.claude/skills/create-issue
Command: npx skills add https://github.com/gitkraken/vscode-gitlens --skill create-issue-gitkraken

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating GitHub issues by analyzing uncommitted changes or existing commits, helping to maintain organized and actionable issue tracking.

Core Features & Use Cases

  • Automated Issue Creation: Generates GitHub issues directly from code changes or commit history.
  • Change Classification: Automatically categorizes changes into bug fixes, features, refactors, etc.
  • Duplicate Detection: Checks for existing similar issues to prevent redundancy.
  • CHANGELOG Integration: Updates the CHANGELOG file with new entries.
  • Use Case: After making several bug fixes, you can use this Skill to automatically create corresponding GitHub issues, classify them as bug fixes, and add them to the [Unreleased] section of your CHANGELOG.

Quick Start

Use the create-issue skill to generate a GitHub issue from your uncommitted changes.

Frequently Asked Questions about create-issue

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

FAQPage Schema
How do I create GitHub issues from uncommitted code changes automatically?

You can create GitHub issues from uncommitted changes by analyzing the Git repository to classify changes, checking for duplicates, and generating structured issue titles and bodies automatically.

Does creating GitHub issues from commits update the CHANGELOG file?

Yes, creating GitHub issues from commits updates the CHANGELOG file by appending relevant entries to the unreleased section, ensuring release tracking remains synchronized with issue management.

Can I prevent duplicate GitHub issues when generating them from code changes?

You can prevent duplicate GitHub issues by using the built-in duplicate detection, which searches GitHub's API for existing similar issues before generating a new one to avoid redundancy.

How does automated issue creation classify Git commits?

Automated issue creation classifies Git commits by analyzing the nature of the changes and categorizing them into bug fixes, features, or refactors to structure the generated issue title and body.

What is the best way to track bug fixes in GitHub issues and CHANGELOGs?

The best way to track bug fixes is to generate GitHub issues from specific commits, automatically classifying them as bug fixes and adding entries to your CHANGELOG to synchronize issue management and release tracking.