handle-issue

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

   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