# Aidd Vcs:04:issue Create

> Create a tracker issue with the configured ticketing tool by gathering a thorough problem description, filling the team template, validating with the user, then opening it. Use when the user says "new issue", "create an issue", "file a bug", "file an issue", "report bug", "open an issue", or invokes `/issue-create`. Do NOT use for committing changes, opening pull requests, tagging releases, or commenting on existing issues.

- Skill: `ai-driven-dev/aidd-vcs-04-issue-create` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add ai-driven-dev/aidd-vcs-04-issue-create`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ai-driven-dev/aidd-vcs-04-issue-create/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: ai-driven-dev (https://skillmd.com/u/ai-driven-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ai-driven-dev/aidd-vcs-04-issue-create

---


# Issue Create

Generates well-formed issues in the project's tracker. Detects the tool from project memory and remote URL, fills the issue template, validates with the user, then creates the issue and returns the URL.

## Available actions

| #   | Action          | Role                                                                       | Input                                  |
| --- | --------------- | -------------------------------------------------------------------------- | -------------------------------------- |
| 01  | `issue-create`  | Detect tool, fill template, validate, open the issue                        | problem_description, labels, type      |

## Default flow

Single action skill. The router dispatches to `issue-create` whenever an issue or bug-report phrase appears.

## Transversal rules

- Detect the ticketing tool from project memory first, then fall back to inspecting `git remote get-url origin`.
- Tool-agnostic: invoke whichever ticketing tool is configured for the project.
- Always wait for explicit user approval of title, body, labels, type, projects, and milestones before creating.
- Issue body follows `assets/issue-template.md`.
- Be thorough and concise. Short sentences. Focus on clarity, reproduction steps, and expected behavior.
- Read `assets/CONTRIBUTING.md` for project-specific issue rules before drafting.

## References

- None.

## Assets

- `assets/issue-template.md`: Issue / ticket body template.
- `assets/CONTRIBUTING.md`: Contribution guidelines, including issue process.

## External data

- None.