Analyze And Create Issue

---
name: analyze-and-create-issue
description: Analyze codebase and create GitHub/GitLab/Forgejo issues per finding
argument-hint: "[optional: domain to focus analysis, e.g., 'security', 'performance', 'documentation']"
user-invocable: true
allowed-tools: Read, Grep, Glob, Skill, Task, Bash(gh:*), Bash(glab:*), Bash(fgj:*), AskUserQuestion
---

# Analyze And Create Issue

Analyze codebase to find improvements. For each improvement:
* Describe concisely to the user and ask if they want to create an issue
* If yes, create the issue in the git repository (GitHub, GitLab, or Forgejo) using the appropriate CLI.

## 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 issues are in the domain of `$argument`. If no `$argument` is provided, consider all types of issues.

3. Get the list of labels for the current project:
   - **GitHub**: `gh label list --repo <owner>/<repo>`
   - **GitLab**: `glab label list`
   - **Forgejo**: `fgj label list -R <owner>/<repo>`

4. For each improvement, Ask the user if they want to create an issue

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

## Issue Content Guidelines

### 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 CLI is unavailable: Inform user to install `gh`, `glab`, or `fgj` and suggest manual creation