moyu-strict

Enforce scoped code edits with a 20-line diff cap.

66|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/uucz/moyu --skill moyu-strict
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moyu-strict
Source: https://github.com/uucz/moyu/tree/main/skills/moyu-strict
Command: npx skills add https://github.com/uucz/moyu --skill moyu-strict

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strict enforcement of minimal, scoped edits to prevent over-engineering and unintended changes during code modifications.

Core Features & Use Cases

  • Zero-tolerance scope checks before edits.
  • 20-line diff cap for single changes.
  • Prohibits creating new files or dependencies without explicit user approval.
  • Prevents drive-by changes to formatting, naming, or import order.

Quick Start

List the files and functions you plan to modify and wait for user confirmation before making any change.

Frequently Asked Questions about moyu-strict

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

FAQPage Schema
How do I enforce minimal code edits and prevent over-engineering during bug fixes?

To enforce minimal code edits, apply strict scope confirmation and a 20-line diff cap before modifying files. This prevents over-engineering by blocking new files, new dependencies, and drive-by formatting changes, ensuring only targeted code edits are executed.

What is scoped code editing and when do I need it for software changes?

Scoped code editing restricts modifications to explicitly confirmed target files and functions. You need it during code reviews, bug fixes, and feature tweaks to prevent unintended changes and maintain strict boundaries across any size codebase.

How do I restrict code modifications to a 20-line diff limit?

You restrict code modifications by imposing a 20-line diff cap for single changes and halting execution until explicit scope confirmation is provided. This enforces zero-tolerance scope checks before applying any code edits to your files.

Can I add new dependencies or create new files while making scoped code edits?

No, you cannot add new dependencies or create new files without explicit user approval. Strict scoped code edits block these actions to prevent scope creep and ensure only necessary, minimal modifications are made to the existing codebase.

Does strict code editing work for large codebases or just small projects?

Strict code editing works across any size codebase. By enforcing a 20-line diff cap and requiring scope confirmation, it effectively prevents over-engineering and unintended changes whether you are working on small tweaks or large software modifications.

Why should I block formatting and import order changes during bug fixes?

Blocking drive-by changes to formatting, naming, or import order during bug fixes prevents unintended code modifications. Strict scope enforcement ensures your code review process focuses solely on the target edits without introducing unrelated diff noise.