mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-19 19:30:29 +08:00
db7f2a6fd5
The official Agent Skills spec (agentskills.io/specification) whitelists exactly 6 top-level frontmatter keys (name/description/license/compatibility/metadata/ allowed-tools). A top-level `origin` key fails the official validator (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate). This moves `origin: X` -> `metadata.origin: X` across the canonical skills/ tree, preserving each value verbatim. Frontmatter-only, minimal diff. - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata) - origin values preserved verbatim (verified 251/251) - YAML validated on all changed files - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors .cursor/.kiro/.agents left untouched; presumably regenerated from canonical) Addresses #2233
44 lines
1.6 KiB
Markdown
44 lines
1.6 KiB
Markdown
---
|
|
name: orch-fix-defect
|
|
description: Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
|
|
metadata:
|
|
origin: ECC
|
|
---
|
|
|
|
# orch-fix-defect
|
|
|
|
Actor · action · target: **orch · fix · defect**. Thin wrapper over the shared
|
|
engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
|
|
|
|
## When to Use
|
|
|
|
- Something is **broken**: wrong output, an error, a crash, a regression.
|
|
- Distinguish from siblings:
|
|
- behavior is correct but you want it different → `orch-change-feature`.
|
|
- the capability does not exist yet → `orch-add-feature`.
|
|
|
|
## Operation settings
|
|
|
|
- **Default size floor:** small (often trivial).
|
|
- **Phase mask:** 0 → (light 2 only if root cause is non-obvious or standard+) →
|
|
4 → 5 → 6. Research (1) is usually skipped.
|
|
- **First move (phase 4):** reproduce the bug as a **new failing** test
|
|
(regression test), then fix until it goes green. Proving the bug exists first
|
|
is what separates a fix from a tweak.
|
|
|
|
## How It Works
|
|
|
|
1. Run the `orch-pipeline` engine with the settings above.
|
|
2. If the root cause is unclear, scope it with `code-explorer` before the red
|
|
test; escalate build breaks to `build-error-resolver` / `/build-fix`.
|
|
3. Stop at **Gate 1** (only if a plan was produced) and **Gate 2** (pre-commit).
|
|
4. Add `security-reviewer` if the defect sits in a security-sensitive path.
|
|
|
|
## Example
|
|
|
|
```
|
|
orch-fix-defect: poller crashes on empty NWS response
|
|
→ write failing test reproducing the crash → fix to green
|
|
→ code-review → commit [GATE 2: confirm] (commit: fix:)
|
|
```
|