Skip to content

fcakyon/claude-codex-settings / plugins/github-dev/skills/create-issue

create-issue

Verified

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".

FileKindSize
SKILL.mdskill md2.6 KB
---
name: create-issue
description: 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".
---

# 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
details, evidence, or a proposed approach only when they help a maintainer act. Keep a
possible implementation separate from the desired outcome.

Remove repeated explanations, promotional claims, conversation history, full diagnostic
dumps, and details that do not help reproduce or resolve the issue. A few useful sections
are better than a long narrative or a checklist of every investigation step.

## Publish or update

Inspect repository guidance and templates, search for an existing issue, and verify the
claims before publishing. When revising, read the current issue and preserve useful
attachments, links, and user edits. Do not expand an issue's scope without user direction.

Use `gh issue create` or `gh issue edit` with `--title` and `--body-file`. To attach
figures, charts, or screenshots directly without a Gist, pass `--attach <path>` (requires
**`gh` >= 2.99.0** and write/push access; up to 50 files per command). Reference local
paths inline in `--body-file` (for example `![Results](./chart.png)`) so `gh` uploads
them to `user-attachments` and rewrites the links in place, or pass `--attach './chart.png#Alt text'`
to append with alt text. Check `gh --version` and upgrade if `--attach` is unavailable.

Read back the published title and body. Link related PRs, but use a closing reference
only when the PR addresses the issue's complete desired outcome.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall