Modify existing features by auditing contracts and wiring seams.
npx skills add https://github.com/AgentSystemLabs/core --skill modify-feature
Please help me install this Agent Skill. Skill: modify-feature Source: https://github.com/AgentSystemLabs/core/tree/main/plugins/agentsystem-core/skills/modify-feature Command: npx skills add https://github.com/AgentSystemLabs/core --skill modify-feature
It helps you make a change to an existing feature without accidentally breaking adjacent contracts, data expectations, UI states, or runtime behavior.
Use modify-feature to extend an existing feature when the change is a tweak or enhancement, for example: "Modify the existing checkout feature to also apply an extra discount when a specific promo code is present, keeping behavior stable elsewhere."
High-intent search queries and answers about installing and using this skill.
To safely modify a feature, you must audit all shifted contracts and adjacent consumers before editing. This is done through pre-flight seam selection and scope boundary confirmation to prevent regressions in types, UI states, or persisted data.
Contract auditing in feature modification is the process of tracing integration points to verify that changes to runtime behavior or data expectations do not break adjacent consumers. It ensures refactor safety by mapping impacted dependencies before applying edits.
Testing edge case coverage when modifying a shipping feature requires running deterministic logic-first tests followed by integration-first runtime-contract tracing. This validates new behavior while confirming existing lifecycle and runtime contracts remain stable.
Yes, you can control integration testing and observability check depths using mode-based risk control. Selecting mode=fast, mode=balanced, or mode=production determines how deeply pre-flight checks and post-edit reviewer subagents evaluate modifications.
The best way to handle security regression and data integrity during a feature enhancement is to apply post-edit reviewer subagents. These automated reviewers specifically audit concurrency, data integrity, and security gaps after modifications are applied.
You should avoid contract audit approaches for feature modification when building entirely new, standalone implementations that do not derive from already-shipping features. This process is designed for extending existing behavior where adjacent consumer risks are present.
0xdeafcafeBackfill retroactive ADRs, Gherkin specs, and characterization tests for existing software features.
espensevExecute tightly scoped code edits and patches within repositories.
apexbusiness-systemsDefine and enforce test-driven development workflows with failing tests first.
azat-ioRestructure code in small steps while preserving external behavior with tests.
