Source profileQuality 80/100

affaan-m/ECC/skills/orch-refine-code/SKILL.md

orch-refine-code

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.

Source repository stars: 234,327
Declared platforms: 0
Static risk flags: 0
Last source update: 2026-07-27
Source checked: 2026-07-28

Decision Compatibility Install Workflow Permissions Evidence Source

Decision brief

What it does—and where it fits

Actor · action · target: orch · refine · code. Thin wrapper over the shared engine in orch-pipeline.

Best for

Same behavior, better structure: extract modules, remove duplication, kill
Distinguish from siblings: if behavior is meant to change at all, this is the

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-refine-code"

Safe inspection promptEditorial

Inspect the Agent Skill "orch-refine-code" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/orch-refine-code/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
When to Use
Same behavior, better structure: extract modules, remove duplication, kill
Same behavior, better structure: extract modules, remove duplication, killDistinguish from siblings: if behavior is meant to change at all, this is the- 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 (or…
02
Operation settings
Default size floor: standard — restructures touch multiple files.
Default size floor: standard — restructures touch multiple files.Phase mask: 0 → 2 (plan the restructure) → 4 (keep green) → 5 → 6. No newFirst move (phase 4): confirm the relevant tests exist and are green
03
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: —…
Run the orch-pipeline engine with the settings above.For dead-code / duplication sweeps, delegate to the refactor-cleaner agentStop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
04
Example
Review the “Example” section in the pinned source before continuing.
Review and apply the “Example” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	80/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	234,327	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: affaan-m/ECC
Skill path: skills/orch-refine-code/SKILL.md
Commit: 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License: MIT
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

orch-refine-code

Actor · action · target: orch · refine · code. Thin wrapper over the shared engine in orch-pipeline.

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

Run the orch-pipeline engine with the settings above.
For dead-code / duplication sweeps, delegate to the refactor-cleaner agent (it runs knip / depcheck / ts-prune and removes safely).
Stop at Gate 1 (restructure plan) and Gate 2 (pre-commit).
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]

Alternatives

Compare before choosing

Computed 10042,015

coreyhaines31/marketingskills

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

Computed 1007

event4u-app/agent-config

design-intelligence

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

Computed 1007

event4u-app/agent-config

existing-ui-audit

Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

Computed 1007

event4u-app/agent-config

testing-anti-patterns

Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions