octanejs/octane / .cursor/skills/handle-issue
handle-issue
VerifiedWork 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.5 KB |
SKILL.md
View on GitHub---
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:
- ...
```
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |