issue-creation

Create clear issue drafts with reproducible context, acceptance criteria, and definition of done.

Skill by imported-and-adapted-by-lucy-camilo

IndexedApache-2.0★ 19

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/camiloandresgtruniandes-issue-creation

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Create clear issue drafts with reproducible context, acceptance criteria, and definition of done. Trigger: when the user asks to open a bug report, feature request, chore, or tracking issue.

Use cases: documents

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 26, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/issue-creation

What's inside

Skill name: issue-creation
Description: Create clear issue drafts with reproducible context, acceptance criteria, and definition of done. Trigger: when the user asks to open a bug report, feature request, chore, or tracking issue.
License: Apache-2.0
Metadata: author: imported-and-adapted-by-lucy-camilo · version: 1.1
Instructions: 44 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# Issue Creation Workflow

## When to Use

Use for drafting or creating actionable backlog items in GitHub, Azure Boards, or another tracker.

## Rules

- Draft issue content first when important details are missing.
- Do not create an external issue unless the user explicitly asks for that write.
- Capture problem statement and expected behavior.
- Include reproducible steps for bugs or concrete scope details for features.
- Add acceptance criteria and definition of done.
- Label issue intent clearly: bug, feature, chore, docs, refactor, security, etc.
- Return created issue URL with a short summary after creation.

## Template

```markdown
## Summary
[One sentence]

## Context / Problem
[What is happening and why it matters]

## Expected Behavior
[What should happen]

## Scope
- [In scope]
- [Out of scope]

## Acceptance Criteria
- [ ] [Concrete, testable criterion]

## Definition of Done
- [ ] Tests/docs/validation updated
- [ ] Security/accessibility/performance considered where relevant

## Evidence
[Logs, screenshots, links, reproduction steps]
```

From CamiloAndresGTRUniandes/lucy-ai, Apache-2.0.

Signals

Stars: 19
Forks: 2
Open issues: 0
Last commit (this folder): Jul 29, 2026 (3 months ago)
Last release: Jul 31, 2026 (2 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version: 1.1
License: Apache-2.0
Repository: github.com/CamiloAndresGTRUniandes/lucy-ai
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from imported-and-adapted-by-lucy-camilo

Cite this page

issue-creation skill. Agent Mart. https://agentmart.dev/skills/camiloandresgtruniandes-issue-creation (last updated 2026-10-24)