What is issue-create-and-handle?

A workflow for turning a reported problem or requested change into one approved GitHub issue and immediately assigning it for implementation. It checks the repository, existing issues, pull requests, and required access before creating anything.

Use it to inspect the codebase, search for duplicates, draft an issue with scheduling headers, get approval, create and assign it, and hand it to the issue-handler.

It prevents duplicate or poorly scoped issues and ensures the issue includes the behavior, acceptance criteria, and test expectations needed for implementation. The issue must be approved before creation.

issue-create-and-handle — Skill for Claude Code and Codex by jonathanung: A workflow for turning a reported problem or requested…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/jonathanung/strike/issue-create-and-handle

Any agent

npx skills add jonathanung/strike --skill issue-create-and-handle

Clone the repo

git clone --depth 1 https://github.com/jonathanung/strike

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jonathanung/strike/issue-create-and-handle.svg)](https://agentmods.dev/skills/jonathanung/strike/issue-create-and-handle)

Your own site

<a href="https://agentmods.dev/skills/jonathanung/strike/issue-create-and-handle"><img src="https://agentmods.dev/badge/skills/jonathanung/strike/issue-create-and-handle.svg" alt="Measured on agentmods" height="20"></a>

Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,015 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00075	$0.01015
Opus 5	$0.00037	$0.00508
Sonnet 5	$0.00015	$0.00203
Haiku 4.5	$0.00007	$0.00102

Measured 5d ago against content hash 61cabbb8b9e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

issue-create-and-handle scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/issue-create-and-handle/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create, approve, assign, and handle an issue

Convert the user's request into one scoped GitHub issue. The issue body must be approved before it is created. Once created, assign it to the authenticated GitHub user and immediately invoke issue-handler for that issue.

Preconditions

gh auth status succeeds.
The current directory is a Git repository with a GitHub remote.
The user has described a problem, change, or outcome.

Stop and ask if authentication, repository access, or the required GitHub permissions are unavailable.

Workflow

Inspect
- Read AGENTS.md and relevant code, tests, and configuration.
- Search existing open issues and PRs for duplicates:
```
gh issue list --state open --limit 100 --search "<key terms> in:title,body"
gh pr list --state open --search "<key terms>"
```
- If an existing issue or PR already covers the request, report it and stop. Do not create a duplicate.
Draft
- State the observed or requested behavior, likely affected area, acceptance criteria, and test expectations.
- Headers are required on every new issue (orchestrator depends on them):
```
wave: 0
depends: none
blocks: none
conflicts: none
priority: bugs-first
```
- Use a concise draft with this body structure:
```
wave: 0
depends: none
blocks: none
conflicts: none
priority: bugs-first

## Problem
...

## Scope
...

## Acceptance criteria
- ...

## Verification
- Tier: A | B | C
- ...
```
- For a feature rather than a bug, use an appropriate wave and priority: feature.
- Set depends / conflicts / blocks from repository evidence:
  - conflicts when the change likely touches the same hotspots as another open issue (keymap/defaults, engine/turn.go, tool registry/defer, shared protocol events) — list those issue numbers.
  - depends when another issue must land first.
- Do not create feature issues with missing headers; refuse and re-draft.

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 100 lines · 75 tokens per session scan A 61cabbb8b9e5

Subscribe to this mod's changes

issue-create-and-handle is a skill published in the GitHub repository jonathanung/strike (5 stars, last pushed 7d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,015 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Project management

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens