Skip to content

Commit 613944a

Browse files
committed
feat: add issue-creator skill for automated issue generation
1 parent b00317c commit 613944a

File tree

1 file changed

+46
-0
lines changed

1 file changed

+46
-0
lines changed
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
name: issue-creator
3+
description: Specialized in creating high-quality GitHub issues following repository-specific templates for bugs and feature requests. Use when asked to report a bug or suggest a feature.
4+
---
5+
# Issue Creator Skill
6+
7+
This skill provides a structured workflow for Gemini CLI to generate and submit well-formatted GitHub issues based on project-specific templates.
8+
9+
## Objective
10+
To streamline the issue creation process by automatically gathering necessary information and applying correct templates, ensuring all relevant details for reproduction or feature justification are captured.
11+
12+
## Workflow Instructions
13+
14+
When invoked to create an issue (bug report or feature request), follow these steps:
15+
16+
1. **Identify Issue Type:**
17+
- Determine if the request is for a **Bug Report** or a **Feature Request**.
18+
19+
2. **Gather Required Information:**
20+
- **For Bug Reports:**
21+
- A clear and concise **Title**.
22+
- **Description:** What is the bug?
23+
- **Steps to Reproduce:** List steps sequentially.
24+
- **Expected vs. Actual Behavior:** What should have happened vs. what actually happened.
25+
- **Environment Details:** OS, Browser, Version (if applicable).
26+
- **Additional Context:** Any other relevant information.
27+
- **For Feature Requests:**
28+
- A clear and concise **Title**.
29+
- **Problem Statement:** What problem does this feature solve?
30+
- **Proposed Solution:** Describe the desired functionality.
31+
- **Alternatives Considered:** Any other ways to solve the problem.
32+
- **Additional Context:** Any other relevant information.
33+
34+
3. **Format the Issue Body:**
35+
- Use the repository's templates found in `.github/ISSUE_TEMPLATE/` as a base for formatting the Markdown body.
36+
- Ensure clear headings and bullet points for readability.
37+
38+
4. **Execute Creation:**
39+
- Use `gh issue create --repo epam/med3web --title "TITLE" --body "BODY"` to create the issue.
40+
- If the user provides labels or assignees, include them using `--label` and `--assignee` flags.
41+
42+
## Constraints
43+
- **Accuracy:** Ensure all "To Reproduce" steps are logical and based on the reported problem.
44+
- **Completeness:** Do not skip sections from the template unless they are truly irrelevant.
45+
- **Tone:** Maintain a professional and helpful tone in the issue description.
46+
- **Verification:** Confirm with the user if any critical information is missing before submitting the issue.

0 commit comments

Comments
 (0)