Source profileQuality 80/100

affaan-m/ECC/skills/orch-change-feature/SKILL.md

orch-change-feature

Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.

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

Decision brief

What it does—and where it fits

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

Best for

  • An existing feature works, but the desired behavior is different ("change",
  • Distinguish from siblings:
  • not broken → not orch-fix-defect (no bug to reproduce).

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

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability 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-change-feature"
Safe inspection promptEditorial

Inspect the Agent Skill "orch-change-feature" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/orch-change-feature/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

  1. 01

    When to Use

    An existing feature works, but the desired behavior is different ("change",

    An existing feature works, but the desired behavior is different ("change",Distinguish from siblings:not broken → not orch-fix-defect (no bug to reproduce).
  2. 02

    Operation settings

    Default size floor: small — most tweaks are a function or two.

    Default size floor: small — most tweaks are a function or two.Phase mask: 0 → (1 only if the new behavior needs research) → light 2 →First move (phase 4): update the existing tests to express the new
  3. 03

    How It Works

    1. Run the orch-pipeline engine with the settings above. 2. Keep the plan light — only standard+ size warrants the full planner pass. 3. Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit). 4. Add security-reviewer if the change touches a security trigger.

    Run the orch-pipeline engine with the settings above.Keep the plan light — only standard+ size warrants the full planner pass.Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
  4. 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
SignalValueEvidence typeMeaning
Quality score80/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
skills/orch-change-feature/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

orch-change-feature

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

When to Use

  • An existing feature works, but the desired behavior is different ("change", "adjust", "make it also …", "instead of X do Y").
  • Distinguish from siblings:
    • not broken → not orch-fix-defect (no bug to reproduce).
    • not new → not orch-add-feature (the capability already exists).

Operation settings

  • Default size floor: small — most tweaks are a function or two.
  • Phase mask: 0 → (1 only if the new behavior needs research) → light 2 → 4 → 5 → 6.
  • First move (phase 4): update the existing tests to express the new desired behavior, then change the implementation until they pass. Changing the tests first is what separates a tweak from a fix.

How It Works

  1. Run the orch-pipeline engine with the settings above.
  2. Keep the plan light — only standard+ size warrants the full planner pass.
  3. Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
  4. Add security-reviewer if the change touches a security trigger.

Example

orch-change-feature: make nws-poller alert at 2 warnings instead of 3
→ update threshold tests to new spec → change impl to green
→ code-review → commit  [GATE 2: confirm]