This skill should be used when the user asks to "create an issue", "file a bug", "report a problem", "rewrite an issue", or "improve an issue title or body".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Create or revise an issue
An issue describes a problem or missing capability. A PR describes a proposed change.
Keep their writing rules separate. For PRs, use [create-pr](../create-pr/SKILL.md).
## Title
Use a concise statement of the problem, naming the affected behavior. Do not use an
imperative change request such as "Fix", "Add", "Enable", or "Keep" as the default.
- "Visitor country is unavailable to upstream apps"
- "GeoIP data becomes stale on running installations"
- "Login returns to the wrong page after checkout"
## Body
Follow the repository's issue template and the user's requested format. Otherwise use:
```markdown
## Problem
One or two sentences naming the failure and its effect.
## Reproduction
1. The relevant setup or version.
2. The smallest steps that demonstrate the problem.
## Current behavior
What was observed, with a short error or result when useful.
## Desired behavior
The outcome the reporter needs.
```
For a missing feature, reproduce the current workflow that exposes the gap. If the
problem was not reproduced, say so instead of inventing steps or results. Add environment
…
The line at the top of this page pins the label git:20261028.e9b34a8, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_6vox37dyfprxibou
GET https://markdownregistry.com/api/v1/resolve?ref=fcakyon/claude-codex-settings/create-issue
GET https://markdownregistry.com/api/v1/blob/58f26dfdbf90f4030587c2f1cd8703041abef3762035132da4c51bdef7d6d5ad
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
fcakyon/claude-codex-settings · plugins/adhd-output-style/skills/adhd-output-style/SKILL.md · This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited…
fcakyon/claude-codex-settings · plugins/aeo/skills/aeo/SKILL.md · This skill should be used when the user asks to "build an AEO strategy", "improve AI search visibility", "track buyer…
fcakyon/claude-codex-settings · plugins/agent-browser/skills/agent-browser/SKILL.md · Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow…
fcakyon/claude-codex-settings · plugins/agent-browser/skills/derive-client/SKILL.md · Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone…
fcakyon/claude-codex-settings · plugins/agent-browser/skills/dogfood/SKILL.md · Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to…
fcakyon/claude-codex-settings · plugins/agent-browser/skills/ui-regression/SKILL.md · This skill should be used when the user asks to "verify UI changes", "audit UI quality", "test every screen and…
fcakyon/claude-codex-settings · plugins/agent-browser/skills/webmcp-gen/SKILL.md · Build and validate experimental WebMCP tools for an existing web page. Use when an agent needs to expose a site's real…
fcakyon/claude-codex-settings · plugins/anthropic-office-skills/skills/docx/SKILL.md · Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word…
qwenlm/qwen-code · .qwen/skills/create-issue/SKILL.md · Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
tobihagemann/turbo · claude/skills/create-issue/SKILL.md · Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue"…
tobihagemann/turbo · codex/skills/create-issue/SKILL.md · Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue"…
mulhamna/jira-commands · plugin/skills/create-issue/SKILL.md · Create new Jira issues with jirac, including interactive prompts for project, issue type, summary, and custom fields
tomzx/agents · skills/create-issue/SKILL.md · Create a GitHub issue with background, prioritized acceptance criteria (Must/Should), and a justified time budget.
nateslabach/skills · skills/create-issue/SKILL.md · Craft a single, high-quality GitHub issue from a developer's description of a bug, unexpected behavior, or desired…
phmatray/tagout · plugins/tagout/skills/create-issue/SKILL.md · Create a fully-seeded GitHub issue — not a bare `issue-create` call: template-compliant, carrying a brainstorm → spec →…
