Restrict code edits to explicitly requested scope and files.
npx skills add https://github.com/uucz/moyu --skill moyu-en
Please help me install this Agent Skill. Skill: moyu-en Source: https://github.com/uucz/moyu/tree/main/codex/moyu-en Command: npx skills add https://github.com/uucz/moyu --skill moyu-en
It helps engineers avoid over-engineering by restricting edits to only what the user explicitly asked for and guiding minimal, targeted changes.
Limit edits to only the files and scopes the user explicitly specified, and ask for confirmation before making any non-essential changes.
High-intent search queries and answers about installing and using this skill.
To prevent over-engineering in code edits, restrict modifications strictly to what was explicitly requested, ensuring minimal, traceable diffs without introducing unnecessary abstractions or dependencies.
The best way to enforce scope control during bug fixes is to limit changes to the requested files and require clarification when the scope is unclear, avoiding unsolicited architectural rewrites.
Achieve minimal diffs for feature tweaks by applying strict scope discipline that forbids new dependencies or architectural changes unless explicitly requested by the user.
Code editing introduces unsolicited dependencies during simple refactors when scope discipline is lacking; enforcing explicit scope boundaries prevents adding non-essential architectural changes.
You should ask for clarification before modifying files outside the requested scope whenever the scope is unclear or non-essential changes seem necessary to complete the task.
LerianStudioGenerate a complete PRD with problem discovery, user stories, and success metrics.
DisposableByDefaultRun pytest unit tests, diagnose failures, and iterate fixes until stable.
nanorepublicaEnforce standardized test-writing guidelines within Claude Code workflows.
tyevansExplore codebases via recursive spikes to generate prioritized task backlogs.
