Agent Skills
› NeverSight/learn-skills.dev
› orch-change-feature
orch-change-feature
GitHub用于修改现有但功能正常的特性，使其行为符合新需求。通过先更新测试用例再调整实现的方式，确保变更可控，并经过代码审查和门禁提交，区别于修复缺陷或新增功能。
Trigger Scenarios
现有功能正常但需调整行为逻辑
需要将功能从状态X改为状态Y
需要增加功能的附加处理能力
Install
npx skills add NeverSight/learn-skills.dev --skill orch-change-feature -g -y
SKILL.md
Frontmatter
{
"name": "orch-change-feature",
"origin": "ECC",
"description": "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."
}
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).
- not broken → not
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-pipelineengine with the settings above. - Keep the plan light — only
standard+ size warrants the fullplannerpass. - Stop at Gate 1 (plan / changed-test approval) and Gate 2 (pre-commit).
- Add
security-reviewerif 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]
Version History
- e0220ca Current 2026-07-05 23:46
