octanejs/octane / .rulesync/skills/triage
triage
VerifiedWork out which part of the octane monorepo owns an unfamiliar failure or task. Use when the area is unclear, before picking a more specific skill.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.5 KB |
SKILL.md
View on GitHub---
targets: ['*']
name: triage
description: Work out which part of the octane monorepo owns an unfamiliar failure or task. Use when the area is unclear, before picking a more specific skill.
---
# Skill: Octane triage
Use this for quick classification of issues, failures, test output, or proposed work.
## Triage dimensions
- **Area:** runtime, compiler, SSR/hydration, Vite plugin, binding package, docs, tests, benchmark, tooling.
- **Type:** bug, feature, parity gap, intentional divergence, performance, flaky test, environment artifact, documentation.
- **Severity:** blocker, high, medium, low.
- **Confidence:** confirmed, likely, unknown, cannot reproduce.
- **Next action:** reproduce, write test, patch, document, defer, ask for info.
## Steps
1. Read `AGENTS.md`.
2. Inspect the concrete files/test output/issue text.
3. Compare against documented intentional divergences.
4. Identify the smallest owner and validation command.
5. Return a concise triage card.
## Triage card template
```md
## Triage
- Area: ...
- Type: ...
- Severity: ...
- Confidence: ...
## Evidence
- ...
## Likely owner
- Files/packages: ...
## Proposed next step
- ...
## Validation
- ...
```
## Label suggestions
- `area:runtime`, `area:compiler`, `area:ssr`, `area:hydration`, `area:vite`, `area:bindings`, `area:docs`, `area:perf`
- `type:bug`, `type:feature`, `type:parity`, `type:divergence`, `type:flaky`, `type:question`
- `priority:blocker`, `priority:high`, `priority:medium`, `priority:low`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |