orch-change-feature

Name: orch-change-feature
Author: affaan-m

Update an existing feature to new behavior with tests, implementation, review, and gated commit.

Stars

★ 229,796

Source

GitHub

Updated

2026-07-15

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 229.8k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "orch-change-feature" skill from askskill:
1. Download https://raw.githubusercontent.com/affaan-m/ECC/main/skills/orch-change-feature/SKILL.md
2. Save it as ~/.claude/skills/orch-change-feature/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Change checkout discount rules

Prompt

Change the existing checkout discount logic from "20 off over 200" to "50 off over 300". First update the related tests to the new rule, then modify the implementation until tests pass, and finally perform a code review and prepare a gated commit message.

Expected

Updated tests, implementation matching the new rule, review notes, and a proper gated commit message.

Adjust search ranking behavior

Prompt

The current search feature works, but the product now requires ranking by relevance first and publish time second instead of publish time first. Update the tests for the new expectation, change the implementation, check regression impact, and provide a commit-ready change summary.

Expected

Tests reflecting the new ranking rule, corresponding code changes, regression risk findings, and a commit summary.

Change notification trigger conditions

Prompt

Change the notification feature from sending immediately after task creation to sending only if the task remains unhandled after 10 minutes. Rewrite or adjust the tests to the new spec, then modify the implementation to satisfy the behavior and complete a review checklist before commit.

Expected

Tests covering delayed triggering, updated business logic implementation, a review checklist, and commit-ready changes.

// docs

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

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).
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]