smithery.ai

draft-issue

Research and draft a high quality GitHub issue before creating it.

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,407 B
  • docs SUMMARY.md 85 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Draft Issue

Use this skill to research the codebase and draft a high quality GitHub issue.

Rules

  • Require an issue topic argument. If missing, ask for it.
  • Research first. Do not draft the issue until you can summarize the current state.
  • User approval is required before running gh issue create.

Workflow

  1. Understand the request

- Restate the request in your own words.

  1. Research the codebase

- Use file search and reads to locate relevant areas. - Identify existing models, controllers, services, migrations, or configs involved.

  1. Summarize findings

- Provide a short summary of what exists today and where.

  1. Draft the issue

- Use the template below.

  1. Get approval

- Ask the user to approve the issue content.

  1. Create the issue

- Use gh issue create with the approved content and labels.

Issue Template

## Context
[Brief background - why is this needed?]

## Current State
[What exists now? Reference files, data, or behavior.]

## Requirements
- Requirement 1
- Requirement 2

## Tasks
- [ ] Task 1
- [ ] Task 2
- [ ] Verification/testing step

## Technical Notes
[Implementation hints, affected areas, gotchas]

Labels

Use GitHub labels like enhancement, bug, task, documentation.