# Create Issue

> Create a well-structured issue in the configured tracker using Feature, Defect, or Task templates.

- **Type:** Skill
- **Install:** `agentstack add skill-meteora-pro-devboy-tools-create-issue`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [meteora-pro](https://agentstack.voostack.com/s/meteora-pro)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** Apache-2.0
- **Upstream author:** [meteora-pro](https://github.com/meteora-pro)
- **Source:** https://github.com/meteora-pro/devboy-tools/tree/main/crates/devboy-skills/skills/01-issue-tracking/create-issue
- **Website:** https://meteora-pro.github.io/devboy-tools/

## Install

```sh
agentstack add skill-meteora-pro-devboy-tools-create-issue
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# create-issue

Turn a free-form user request into a structured ticket the team can actually work on. The skill picks one of three templates, fills it, creates the issue, and (optionally) attaches reproduction details or logs as a follow-up comment.

## When to use

- The user describes a bug, a feature idea, or a piece of work without a ticket yet.
- Another skill discovered something worth filing (e.g. `review-mr` flagged a deeper issue).
- The user asks to "open a ticket for this" in the middle of a longer conversation.

## Procedure

### 1. Pick the template

Classify the request before writing anything. The three templates share the same shape — swap the word and tweak the slots.

**Feature** — new capability, user-visible change, or design work.

```markdown
## Title
, e.g. "Add bulk archive to issue list"

## Context
Who asked for this and why. Link the user conversation or meeting note.

## Acceptance criteria
- [ ] Observable behaviour #1
- [ ] Observable behaviour #2
- [ ] Docs / changelog updated

## Notes
Design sketches, open questions, out-of-scope.
```

**Defect** — something is demonstrably broken.

```markdown
## Title
: , e.g. "Dashboard: pipeline badge shows stale status after retry"

## Context
Environment, version, user impact. Link the failing run / screenshot / log if there is one.

## Acceptance criteria
- [ ] Steps to reproduce no longer trigger the bug
- [ ] Regression test covers the fix
- [ ] Release note drafted

## Notes
Suspected root cause, related incidents.
```

**Task** — chore, refactor, docs, infra, anything that is not a user-facing feature and not a bug.

```markdown
## Title
: , e.g. "Infra: rotate CI signing keys"

## Context
Why now, what it unblocks.

## Acceptance criteria
- [ ] The concrete thing is done
- [ ] Follow-up tickets filed for anything we deliberately punted

## Notes
```

### 2. Create the issue

Pass the title and the rendered Markdown body to `create_issue`:

```bash
devboy tools call create_issue '{
  "title": "Dashboard: pipeline badge shows stale status after retry",
  "description": "## Context\nSeen by @alice on prod v2.4.1. The badge keeps the first status after a manual retry.\n\n## Acceptance criteria\n- [ ] Badge refreshes within 5s of retry\n- [ ] Regression test covers the fix\n\n## Notes\nSuspected cache miss in `PipelineStatusService`.",
  "labels": ["bug", "dashboard"],
  "assignees": ["alice"]
}'
```

On Windows, JSON needs escaped quotes:

```cmd
devboy tools call create_issue "{\"title\": \"...\", \"description\": \"...\"}"
```

Useful optional fields: `parentId` (ClickUp subtasks), `issueType` (Jira: `Task` / `Bug` / `Story`), `projectId` (Jira project key override), `markdown: false` when the description is plain text.

### 3. Attach reproduction details as a comment

Keep the description tight — offload long logs, stack traces, or screenshots to a comment. `add_issue_comment` takes the key returned by step 2:

```bash
devboy tools call add_issue_comment '{
  "key": "DEV-789",
  "body": "Full stack trace from staging:\n\n```\nReferenceError: ...\n```"
}'
```

On ClickUp, the same tool accepts `attachments` for small files (each ≤ 10 MB, base64-encoded).

### 4. Confirm the result

Read the new issue back so the user sees exactly what was filed:

```bash
devboy tools call get_issue '{"key": "DEV-789"}'
```

## Success criteria

- The created issue has a clear title, a populated body following the chosen template, and the right labels / assignees.
- Any reproduction material lives in a comment rather than bloating the description.
- The agent reports the new issue key back to the user so they can link it elsewhere.

## Non-goals

- This skill does not triage or reassign existing issues — that is `update-issue`.
- It does not link issues together — that is `link-issues`.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [meteora-pro](https://github.com/meteora-pro)
- **Source:** [meteora-pro/devboy-tools](https://github.com/meteora-pro/devboy-tools)
- **License:** Apache-2.0
- **Homepage:** https://meteora-pro.github.io/devboy-tools/

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-meteora-pro-devboy-tools-create-issue
- Seller: https://agentstack.voostack.com/s/meteora-pro
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.