mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-18 18:40:16 +08:00
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
45 lines
1.8 KiB
Markdown
45 lines
1.8 KiB
Markdown
---
|
|
name: orch-refine-code
|
|
description: Orchestrate a behavior-preserving refactor — confirm tests are green, restructure without changing behavior, keep tests green, review, and gated commit. Use when the structure should improve but behavior must not change.
|
|
metadata:
|
|
origin: ECC
|
|
---
|
|
|
|
# orch-refine-code
|
|
|
|
Actor · action · target: **orch · refine · code**. Thin wrapper over the shared
|
|
engine in [`orch-pipeline`](../orch-pipeline/SKILL.md).
|
|
|
|
## When to Use
|
|
|
|
- Same behavior, **better structure**: extract modules, remove duplication, kill
|
|
dead code, reduce nesting, rename for clarity.
|
|
- Distinguish from siblings: if behavior is meant to change at all, this is the
|
|
wrong skill (`orch-change-feature` / `orch-fix-defect`).
|
|
|
|
## Operation settings
|
|
|
|
- **Default size floor:** standard — restructures touch multiple files.
|
|
- **Phase mask:** 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No new
|
|
behavior tests are written — the existing suite is the safety net.
|
|
- **First move (phase 4):** confirm the relevant tests exist and are **green
|
|
before** touching code; if coverage is thin, add characterization tests first.
|
|
Then restructure in small steps, re-running tests after each.
|
|
|
|
## How It Works
|
|
|
|
1. Run the `orch-pipeline` engine with the settings above.
|
|
2. For dead-code / duplication sweeps, delegate to the `refactor-cleaner` agent
|
|
(it runs knip / depcheck / ts-prune and removes safely).
|
|
3. Stop at **Gate 1** (restructure plan) and **Gate 2** (pre-commit).
|
|
4. Commit as `refactor:` — the diff must be behavior-neutral.
|
|
|
|
## Example
|
|
|
|
```
|
|
orch-refine-code: extract the NWS HTTP client out of poller.py
|
|
→ confirm tests green → plan extraction [GATE 1: approve]
|
|
→ move in small steps, tests green throughout → code-review
|
|
→ commit refactor: [GATE 2: confirm]
|
|
```
|