How do I install the Aidd Vcs:04:issue Create skill?

Run npx skillmds@latest add ai-driven-dev/aidd-vcs-04-issue-create in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aidd Vcs:04:issue Create safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Vcs:04:issue Create?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aidd Vcs:04:issue Create free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aidd Vcs:04:issue Create?

ai-driven-dev (@ai-driven-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidd Vcs:04:issue Create by ai-driven-dev

Name: Aidd Vcs:04:issue Create
Author: ai-driven-dev

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.

ai-driven-dev 6ccd7a9 5 files · 6.6 KB Updated Sep 17, 2026

File contents

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.

---name: aidd-vcs-04-issue-createdescription: 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.---# Issue CreateGenerates 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 flowSingle 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.

Frequently asked questions