How do I install the Handle Issue skill?

Run npx skillmds@latest add octanejs/handle-issue-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Handle Issue safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Handle Issue?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Handle Issue free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Handle Issue?

octanejs (@octanejs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Handle Issue by octanejs — Agent Skill

Name: Handle Issue
Author: octanejs

File contents

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

Fetch issue context

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

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

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.
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.
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.
Propose solution Include:
- root-cause hypothesis
- files likely to change
- test plan
- compatibility/divergence considerations
- risk level
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.
Issue response template

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

Findings:
- ...

Likely cause:
- ...

Proposed fix:
- ...

Validation plan:
- ...

Notes:
- ...

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.

---name: handle-issue-3description: 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 issueUse 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.## Workflow1. **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 level6. **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**```mdThanks: I triaged this as <classification> affecting <area>.Findings:- ...Likely cause:- ...Proposed fix:- ...Validation plan:- ...Notes:- ...```8. **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.

Frequently asked questions

Handle Issue