skills.rest
uucz
uuczCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

moyu-lite

Restrict code edits to the user-specified scope during patch reviews.

66|1|Updated Mar 23, 2026
Search Tags:#clarification#guardrail#over-engineering#code-editing#minimal-diff#scope-control#refactor-safety
One-click install
npx skills add https://github.com/uucz/moyu --skill moyu-lite
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moyu-lite
Source: https://github.com/uucz/moyu/tree/main/skills/moyu-lite
Command: npx skills add https://github.com/uucz/moyu --skill moyu-lite

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight anti-over-engineering guard that activates when edits extend beyond user intent, keeping code changes lean and focused.

Core Features & Use Cases

  • Enforces scope-limited edits to only what the user asked
  • Reduces unnecessary refactoring and abstraction
  • Use Case: during code reviews or patch submissions, blocks unrequested structural changes while allowing targeted fixes

Quick Start

Provide a minimal patch that only changes explicitly requested files.

Frequently Asked Questions about moyu-lite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent over-engineering during code refactoring?▼

To prevent over-engineering during code refactoring, enforce explicit scope control and favor minimal diffs. This restricts code edits strictly to user-specified requests, blocking unrequested structural changes and unnecessary abstraction.

What is scope control in code editing and patch reviews?▼

Scope control in code editing limits modifications to explicitly requested files and features. During patch reviews, it blocks unrequested structural changes while allowing targeted fixes, ensuring changes remain lean and focused.

How do I restrict AI code edits to minimal diffs?▼

Restrict AI code edits to minimal diffs by applying guardrails that enforce user-specified scope. This prompts for clarification when the desired reach is unclear, preventing unnecessary refactoring and broad diffs.

Why does my code patch include unrequested structural changes?▼

Your code patch includes unrequested structural changes due to scope creep during refactoring. Applying anti-over-engineering guardrails restricts edits to the original intent, favoring minimal diffs and prompting for clarification.

When should I prompt for clarification during feature additions?▼

Prompt for clarification during feature additions when the desired reach of code edits is unclear. This scope control mechanism prevents over-engineering by ensuring modifications align strictly with explicit user intent.

Related Skills

Explore More Software Engineering Skills→
LerianStudioLerianStudio
205

pre-dev-prd-creation

Generate a complete PRD with problem discovery, user stories, and success metrics.

Official
Basic
baekenoughbaekenough
13

pr-auto-improve

Analyze pull requests to generate targeted code-quality improvement reports.

Community
Advanced
AcosmiAcosmi
6

apply-patch

Apply structured multi-file patches with Add, Update, Delete, and Move operations.

Community
Intermediate
uuczuucz
66

moyu-en

Restrict code edits to explicitly requested scope and files.

Community
Advanced