本文へ移動
cccskills
無料GitHub で公開

handle-issue

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.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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
    • 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

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

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.

日本語の概要は準備中です。原文の説明を表示しています。

octanejs/octane1,4572026年10月11日 更新

octanejs のスキルをすべて見る

このスキルの問題を報告する