New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Handle Issue

by octanejs in octanejs/octane

Work a GitHub issue in the octane repo. An agent skill from octanejs/octane.

MITAuto-check passedDevelopment

Install Handle Issue

skills CLI
$ npx skills add octanejs/octane --skill handle-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install octanejs/octane handle-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/octanejs/octane.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/handle-issue .claude/skills/handle-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
handle-issue
GitHub stars
1.5k
Token cost
~638 tokens
SKILL.md length
246 words
Files
1
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Work a GitHub issue in the octane repo. An agent skill from octanejs/octane.

  • Works in 8 steps: Fetch issue context → Classify → Check project rules → …
  • Given an issue number
  • SKILL.md covers Inputs and Workflow
  • Calls gh

What it does

Handle Issue is an agent skill from octanejs/octane. Work a GitHub issue in the octane repo. Use when given an issue number or link. Fetches the issue, classifies the owning area, and plans the fix.

Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub and React. The repository describes itself as: React’s programming model, compiled. The successor to Inferno. The licence is MIT.

When your agent uses it

  • Given an issue number

Example prompts

  • “/handle-issue”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Fetch issue context
  2. Classify
  3. Check project rules
  4. Reproduce or validate claim
  5. Propose solution
  6. Optional implementation
  7. Issue response template
  8. Labels/comments

What it can do on your machine

Read from SKILL.md and the folder at commit 4cc2a1e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Handle Issue loads about 638 tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 246 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~638

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from octanejs/octane at commit 4cc2a1e, republished under its MIT licence (© octanejs). 246 words, ~638 tokens.

Download SKILL.mdSave it as .claude/skills/handle-issue/SKILL.md (or your agent's skills folder).
name
handle-issue
description
Work a GitHub issue in the octane repo. Use when given an issue number or link. Fetches the issue, classifies the owning area, and plans the fix.

Skill: Handle an Octane GitHub issue

Use this to inspect an issue, triage it, propose a solution, and optionally implement it.

Inputs

  • Issue number or URL.
  • Optional scope constraints: triage-only, propose-only, implement, or create PR.

Workflow

  1. Fetch issue context

    bash
    gh issue view <number> --json number,title,body,author,labels,state,comments,assignees,milestone,url

    If linked PRs/commits are mentioned, inspect them too.

  2. Classify

    • bug, feature, docs, test gap, performance, parity gap, ecosystem binding, question.
    • affected area: core runtime, compiler, SSR/hydration, Vite plugin, binding package, benchmarks/docs.
    • severity and likely user impact.

  3. Check project rules

    • Read AGENTS.md, docs/packages.md, and relevant docs.
    • For React-behavior issues, check docs/differences-from-react.md and classify intentional divergence vs bug.

  4. Reproduce or validate claim

    • Prefer a minimal failing test or fixture.
    • If not reproducible, document missing info and ask targeted questions.
    • Avoid broad rewrites before there is a failing test.

  5. Propose solution Include:

    • root-cause hypothesis
    • files likely to change
    • test plan
    • compatibility/divergence considerations
    • risk level

  6. Optional implementation

    • Follow bug-hunter.md for bugs.
    • Follow octane-react-library-port for binding/compat issues.
    • Follow octane-core-extend.md for runtime/compiler extensions.

  7. Issue response template

md
Thanks: I triaged this as <classification> affecting <area>.

Findings:
- ...

Likely cause:
- ...

Proposed fix:
- ...

Validation plan:
- ...

Notes:
- ...
  1. Labels/comments
    • Use gh issue edit/gh issue comment only when asked or when operating autonomously with permission.
    • Do not close issues without maintainer instruction unless explicitly authorized.
    • Classify issues with the existing bug/enhancement/documentation/question set. The feat/fix/docs/test/perf/refactor/chore/ci type labels are for PRs.
    • Add agent-authored to an issue an agent filed. When an agent only comments on someone else's issue, say so in the comment rather than relabelling their issue.
    • A PR that closes the issue is labelled by create-a-pr, not here.

© octanejs, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/handle-issue of octanejs/octane.

Open the folder on GitHubat commit 4cc2a1e

Compare with similar skills

Handle Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Handle Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Handle Issue this skilloctanejs/octane1.5k—~638Automated safety check: PassMIT
Run Paritymillionco/react-doctor15k—~4.1kAutomated safety check: PassCustom licence
Cherry Studio PR ReviewCherryHQ/cherry-studio53k—~3.9kAutomated safety check: PassAGPL-3.0
Deepseek Automationzhu1090093659/deepseek-pp1.9k—~2.1kAutomated safety check: NotesApache-2.0
React Expertreactjs/ar.react.dev1642 repos~2.7kAutomated safety check: PassCC-BY-4.0
Gh Release Notesreact-cosmos/react-cosmos8.7k—~335Automated safety check: PassMIT

Similar skills

  • Run Parity

    millionco/react-doctor

    Compare React Doctor diagnostics for a GitHub pull request (PR) with Vercel Sandbox.

    15k GitHub stars~4.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Cherry Studio PR Review

    CherryHQ/cherry-studio

    Reviews Cherry Studio branches, pull requests, commits, files and docs against the project's own architecture, naming, API-boundary and UI rules, report-only by default.

    53k GitHub stars~3.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Deepseek Automation

    zhu1090093659/deepseek-pp

    A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • React Expert

    reactjs/ar.react.dev

    Official

    A skill your agent uses when researching React APIs or concepts for documentation.

    164 GitHub starsUsed in 2 repos~2.7k tokens
    DevelopmentAuto-check passed

  • Gh Release Notes

    react-cosmos/react-cosmos

    Generate a clean list of commits between two git tags for GitHub release notes.

    8.7k GitHub stars~335 tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • Implement GitHub Feature

    AgnosticUI/agnosticui

    Design and implement a new feature or component from a GitHub issue.

    827 GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from octanejs/octane

All 19 skills in this repo

  • Performance Audit

    octanejs/octane

    Audit or defend Octane performance. An agent skill from octanejs/octane.

    1.5k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • Update Bindings

    octanejs/octane

    Audit one, several, or all existing Octane bindings; implement selected maintenance findings or remove redundant copied files with evidence matched to source ownership.

    1.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

  • Concise Code

    octanejs/octane

    Keep a change small and in the existing idiom - size the plan and weigh smaller alternatives before writing it, reuse the mechanism that already owns the behavior instead of adding a parallel one…

    1.5k GitHub stars~2.3k tokensUpdated today
    Auto-check passed

  • Migrate V8 To V9

    octanejs/octane

    Perform a complete @tanstack/react-table v8-to-v9 migration: hook and feature architecture, row-model slots, React state and subscriptions, rendering, composable tables, type helpers, and every…

    1.5k GitHub stars~4.7k tokensUpdated today
    Auto-check passed

  • Octane React Library Port

    octanejs/octane

    Implement and verify new React-library ports or copied/rewritten React surfaces in Octane bindings from npm names or npm/GitHub links/lists.

    1.5k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Triage

    octanejs/octane

    Work out which part of the octane monorepo owns an unfamiliar failure or task.

    1.5k GitHub stars~374 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Handle Issue

What does Handle Issue do?

Work a GitHub issue in the octane repo. An agent skill from octanejs/octane. Handle Issue is an agent skill from octanejs/octane. Work a GitHub issue in the octane repo.

When should I use Handle Issue?

Handle Issue fits situations like: given an issue number.

How do I install Handle Issue in Claude Code?

Run `npx skills add octanejs/octane --skill handle-issue -a claude-code`. Or copy the skill folder (.agents/skills/handle-issue in octanejs/octane) into .claude/skills/handle-issue in your project. Claude Code loads it when a task matches its description.

How do I install Handle Issue in Codex?

Run `npx skills add octanejs/octane --skill handle-issue -a codex`. Or copy the skill folder (.agents/skills/handle-issue in octanejs/octane) into .agents/skills/handle-issue in your project. Codex loads it when a task matches its description.

Can I use Handle Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add octanejs/octane --skill handle-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/handle-issue, .gemini/skills/handle-issue, .github/skills/handle-issue and .opencode/skills/handle-issue in your project.

What does Handle Issue need to run?

Going by SKILL.md and its folder, Handle Issue needs the command-line tools its instructions call (gh).

Does Handle Issue access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Handle Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Handle Issue use?

Handle Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Handle Issue use?

About 638 tokens (SKILL.md is roughly 2.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Handle Issue?

Skills that share tags, products or a category with Handle Issue: Run Parity (millionco/react-doctor, 15k stars), Cherry Studio PR Review (CherryHQ/cherry-studio, 53k stars), Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars) and React Expert (reactjs/ar.react.dev, 164 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Handle Issue?

octanejs (a GitHub organization) maintains it in octanejs/octane, which has 1,455 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 10, 2026.

Source: octanejs/octane on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.