# Issue Creation

> Creates professional GitHub issues—bug reports, feature requests, and technical tasks—with clear context, acceptance criteria, and labels for immediate action.

- Skill: `leandrobenjaminl/issue-creation` (Agent Skill)
- Install (CLI): `npx skillmds@latest add leandrobenjaminl/issue-creation`
- Raw SKILL.md: https://api.skillmd.com/api/skills/leandrobenjaminl/issue-creation/raw
- Safety review: PASS (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools, Productivity, Task Management
- Tags: Bug Report, Feature Request, Github, Issue Tracking, Labels, Milestones, Technical Task
- License: MIT
- Author: LeandroBenjaminL (https://skillmd.com/u/leandrobenjaminl)
- Updated: 2026-08-22
- Page: https://skillmd.com/skills/leandrobenjaminl/issue-creation

---


# Skill: issue-creation

Professional issues. Clear enough that anyone can pick them up.

## Trigger

- You found a bug and need to report it
- You want to propose a new feature
- A large project needs to be broken down into tasks
- You were assigned an issue and need to understand it

## Workflow LEND

1. ANALYZE
   ├── Type: bug, feature, chore, improvement
   ├── Severity: critical, major, minor, suggestion
   ├── Context: where does it happen? how to reproduce?
   └── Priority: now, this week, this month, backlog

2. OFFER (Senior Menu)
   ├── A) Bug report — reproduction steps + expected vs actual + environment
   ├── B) Feature request — description + motivation + acceptance criteria
   └── C) Technical task — context + definition of done + subtasks

3. CHOOSE → user confirms

4. EXECUTE
   ├── Bug: clear title, steps to reproduce, expected vs actual, logs/screenshots, environment
   ├── Feature: title, description, motivation, acceptance criteria (Given/When/Then)
   ├── Labels: bug, feature, enhancement, good-first-issue, needs-discussion
   ├── Assignee: who will resolve it
   ├── Milestone: if applicable (sprint, version)
   ├── Priority label: P0 (critical), P1 (high), P2 (medium), P3 (low)
   └── Templates: use issue template if the repo has one

5. VERIFY
   ├── The issue has all the information needed to start
   ├── Reproduction steps are clear (for bugs)
   └── Acceptance criteria are measurable (for features)

- [ ] Save decisions and changes to Engram (mem_save)
- [ ] Check if README, AGENTS.md, or ARCHITECTURE.md need updating
- [ ] If docs changed → update them in the same PR/commit