issue-dips

Generate GitHub issues with codebase context and labels via GitHub CLI.

Updated Mar 24, 2023
One-click install
npx skills add https://github.com/j4hr3n/dotfiles --skill issue-dips
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-dips
Source: https://github.com/j4hr3n/dotfiles/tree/main/configs/claude-code/skills/issue-dips
Command: npx skills add https://github.com/j4hr3n/dotfiles --skill issue-dips

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate well-researched GitHub issues with codebase context.

Core Features & Use Cases

  • Explore the codebase to gather context and prior art relevant to the issue.
  • Draft a focused issue body with sections: Context, Description, Acceptance criteria, and Technical notes.
  • Target repository and labeling: Ensure issues are created in DIPSDev/agents with appropriate labels.

Quick Start

Describe the issue you want to file in plain language and I will draft a complete GitHub issue ready for review.

Frequently Asked Questions about issue-dips

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

FAQPage Schema
How do I generate a GitHub issue with codebase context automatically?

To generate a GitHub issue with codebase context, describe the issue in plain language. The Skill explores the codebase for relevant prior art, drafts a structured body with Context, Description, Acceptance criteria, and Technical notes, then confirms with you before creating it via GitHub CLI.

What's the best way to draft a structured bug report for a feature request?

Drafting a structured bug report or feature request is best handled by guiding you through codebase exploration to gather context. It formats the issue body into Context, Description, Acceptance criteria, and Technical notes, ensuring well-researched content before opening the issue.

Does this GitHub issue automation tool work with the DIPSDev/agents repository?

Yes, this GitHub issue automation tool explicitly targets the DIPSDev/agents repository. It ensures issues are created there with appropriate labels, enforcing a structured workflow that includes target repository selection and label assignment prior to confirmation.

Why do I need to confirm before the GitHub CLI creates an issue?

You need to confirm before the GitHub CLI creates an issue to review the drafted content, verify the codebase context, and ensure the assigned labels are correct. This user confirmation step prevents incorrect or unwanted issues from being created automatically.

Can I use plain language to file a bug ticket without writing the markdown myself?

Yes, you can use plain language to file a bug ticket without writing markdown yourself. Describe the issue you want to file, and the Skill drafts a complete, formatted GitHub issue with the required sections ready for your review.