Skip to content

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

create-issue

Unverified

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.

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:

## 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. 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: 463kUpdated Claude CodeCodexVerifiedInstall
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: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall