Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

04-issue-create

Sterne206

Forks15

Aktualisiert10. Juli 2026 um 10:57

Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

ai-driven-dev

ai-driven-dev/framework

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

Datei-Explorer

4 Dateien

SKILL.md

readonly

name	04-issue-create
description	Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.

Issue Create

Files well-formed issues in the configured tracker after gathering enough context to be actionable.

Actions

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

Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

Detect the ticketing tool from project memory first, then fall back to inferring it from the remote URL.
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.

Assets

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

Mehr aus diesem Repository

gleiches Repository

02-project-memory

ai-driven-dev/framework

Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.

2026-07-13206

00-onboard

ai-driven-dev/framework

Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.

2026-07-10206

01-bootstrap

ai-driven-dev/framework

Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.

2026-07-10206

03-context-generate

ai-driven-dev/framework

Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.

2026-07-10206

04-skill-generate

ai-driven-dev/framework

Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.

2026-07-10206

05-rule-generate

ai-driven-dev/framework

Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.

2026-07-10206

name	04-issue-create
description	Create an issue in the configured ticketing tool. Use when the user wants to file a bug, open an issue, or report a problem. Not for committing, opening a pull request, or commenting on an existing issue.

Issue Create

Files well-formed issues in the configured tracker after gathering enough context to be actionable.

Actions

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

Before running an action, read its file in actions/, not only the table or assets.

Transversal rules

Detect the ticketing tool from project memory first, then fall back to inferring it from the remote URL.
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.

Assets

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