Create Issue

---
name: create-issue
description: Create formatted GitHub/GitLab/Forgejo issue with approval
argument-hint: "<issue-topic-or-description>"
user-invocable: true
disable-model-invocation: true
allowed-tools: Read, Grep, Glob, Skill, Bash(gh:*), Bash(glab:*), Bash(fgj:*), AskUserQuestion
---

# Create Issue

Create an issue for the current git repository. This skill automatically detects whether the repository is hosted on GitHub, GitLab, or Forgejo and uses the appropriate CLI tool (`gh`, `glab`, or `fgj`).

## Process

1. **Detect Repository Host**: Use the `detect-repo-host` skill to identify the hosting service (GitHub, GitLab, or Forgejo) and extract owner/repo details.

2. **Validate Arguments**: Ensure the issue topic/description is provided as `$argument`

3. Always list available labels before creating the issue. Do not add labels that do not exist in the host repository.
   - **GitHub**: Use `gh label list --repo <owner>/<repo>` via Bash
   - **GitLab**: Use `glab label list`
   - **Forgejo**: Use `fgj label list -R <owner>/<repo>`

4. **Create Issue**: Use the appropriate CLI tool:
   - **GitHub**: Use `gh issue create --repo <owner>/<repo> --title "<title>" --body "<body>" --label "<label1>" --label "<label2>"`
   - **GitLab**: Use `glab issue create --title "<title>" --description "<body>" --label "<label1>" --label "<label2>"`
   - **Forgejo**: Use `fgj issue create -R <owner>/<repo> -t "<title>" -b "<body>" -l <label1> -l <label2>`

5. **Request Permission**: Always ask the user for permission before creating the issue

## Issue Content Guidelines

The issue content should be based on: `$argument`

### Requirements:
- **Title**: Clear, concise summary (max 80 characters)
- **Description**: Detailed explanation including:
  - Problem description or feature request
  - Steps to reproduce (if bug)
  - Expected behavior
  - Current behavior
  - Additional context or screenshots
- **Labels**: Suggest appropriate labels based on those available in the host repository.

### Formatting:
- Use proper markdown formatting
- Include code blocks with syntax highlighting when relevant
- Add checklists for actionable items
- Reference related issues or PRs when applicable

## Error Handling

- If repository host detection fails: The `detect-repo-host` skill provides detailed error messages (not a git repo, no remotes, unsupported host)
- If `gh`/`glab`/`fgj` CLI not installed: Inform user and suggest installing the appropriate CLI tool

## Example Usage

```
/create-issue "Add dark mode toggle to user preferences"
```

This will create an issue with proper formatting, context, and request user confirmation before proceeding.