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.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Use this to inspect an issue, triage it, propose a solution, and optionally implement it.
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
Check project rules
AGENTS.md, docs/packages.md, and relevant docs.docs/differences-from-react.md and classify intentional divergence vs bug.Reproduce or validate claim
Propose solution Include:
Optional implementation
bug-hunter.md for bugs.octane-react-library-port for binding/compat issues.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:
- ...
gh issue edit/gh issue comment only when asked or when operating autonomously with permission.bug/enhancement/documentation/question set. The
feat/fix/docs/test/perf/refactor/chore/ci type labels are for PRs.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.create-a-pr, not here.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Write a new Octane component in .tsrx, convert JSX to .tsrx, or add scoped <style> blocks and themes. Use when creating a .tsrx file rather than editing one, because the path-scoped tsrx-authoring rule only fires once such a file is open.
The English summary is being prepared. Showing the original description.
Find and fix a bug in the octane monorepo. Use when given a failing test, a regression, or a report that behavior differs from expectation, including deciding whether a React mismatch is an intentional divergence.
The English summary is being prepared. Showing the original description.
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, and simplify the diff before handoff. Use when planning any change beyond a few lines, before readying a PR, or when reviewing agent-written code for bloat.
The English summary is being prepared. Showing the original description.
Open a pull request for octane work. Load before creating the branch, commit, changeset, or PR, including when opening a PR is the tail step of a task that was about something else.
The English summary is being prepared. Showing the original description.
Change Octane's runtime, compiler, scheduler, reconciler, SSR, or hydration engine. Use before editing packages/octane/src. Covers the observable contract, hot-path analysis, and the performance evidence required before handoff.
The English summary is being prepared. Showing the original description.
Implement and verify new React-library ports or copied/rewritten React surfaces in Octane bindings from npm names or npm/GitHub links/lists. Enforces immutable provenance, license boundaries, dependency ordering, full-surface parity, and machine evidence. Existing-binding audits and maintenance start with update-bindings.
The English summary is being prepared. Showing the original description.