---
name: octanejs-resolve-octane-defect
description: "Resolve a defect discovered in Octane or an Octane library with a correct fix PR or actionable issue in the owning repository instead of a workaround."
license: "MIT"
metadata:
  decimalai-skill-id: "2adc344d-481b-4c1b-a81b-e906ed3c8a1f"
  decimalai-version-id: "d1077425-690f-4974-b685-e0d7106dc033"
  decimalai-version: "1"
  decimalai-body-sha256: "f2c59921b686f2fbc47681d9c8be52879d66d080e03fbf366a59785ca907d9cd"
  decimalai-name: "octanejs/resolve-octane-defect"
  decimalai-format: "1"
  decimalai-invocation: "model"
  decimalai-category: "coding"
  decimalai-source: "https://app.decimal.ai/s/octanejs-resolve-octane-defect@1/SKILL.md"
---
# Resolve an Octane defect

Establish that the behavior is a defect and identify the package and repository
that own it; use `bug-hunter` for diagnosis and `triage` if ownership is unclear.

- If the correct fix is understood and fits the task, reuse an existing fix PR
  or fix the owning source, add regression coverage there, and open a PR. Link
  any existing issue and retain any consumer scenario as integration evidence.
  Use `create-a-pr` for this repository; follow the owning repository's
  instructions elsewhere.
- Otherwise, reuse an existing issue or create one in the owning repository with the
  affected package/version, expected and actual behavior, a minimal reproduction
  or the best available evidence, and why the fix remains open. Label an
  agent-filed Octane issue `agent-authored`, as described in `handle-issue`.
  Keep private consumer code and data out of public reports.

Link the issue or PR from the original work when applicable and state what
remains blocked. Do not substitute a workaround for the owner-level fix or issue.