MetaClaw avoid-scope-creep

Common mistake — doing unrequested work (refactoring, adding extra features, cleaning up style) when the user asked for a specific, targeted change. Only change what was explicitly asked.

install
source · Clone the upstream repo
git clone https://github.com/aiming-lab/MetaClaw
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/aiming-lab/MetaClaw "$T" && mkdir -p ~/.claude/skills && cp -r "$T/memory_data/skills/avoid-scope-creep" ~/.claude/skills/aiming-lab-metaclaw-avoid-scope-creep && rm -rf "$T"
manifest: memory_data/skills/avoid-scope-creep/SKILL.md
source content

Avoid Scope Creep

Mistake pattern: User asks to fix a specific bug → you also refactor the function, rename variables, add docstrings, and restructure the file → harder to review, introduces new risk.

Rule: Only change what was asked. If you notice other issues while working, mention them as a note rather than silently fixing them.

Exception: If a requested change is impossible without fixing a directly blocking dependency, fix the minimum required dependency and explain why.

Anti-pattern:

while I'm here, I also improved...
without being asked.