moyu-ko

Name: moyu-ko
Availability: InStock
Author: uucz

Suppress over-engineering by applying only user-requested changes during reviews and edits.

66|1|Updated Mar 23, 2026

Search Tags:#refactoring #minimalism #code-review #guardrails #change-management #team-productivity #overengineering

Ready to run

npx skills add https://github.com/uucz/moyu --skill moyu-ko

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moyu-ko
Source: https://github.com/uucz/moyu/tree/main/skills/moyu-ko
Command: npx skills add https://github.com/uucz/moyu --skill moyu-ko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

과잉 엔지니어링 패턴이 감지되면 자동으로 활성화됩니다: 이는 팀이 불필요한 추상화나 전체 리팩토링으로 이어지는 변경을 막아줍니다.

Core Features & Use Cases

자동 활성화 및 경계: 사용자가 명시적으로 요청하지 않은 변경은 적용되지 않도록 제어합니다.
철칙 준수 가이드: 3가지 원칙을 통해 최소한의 편집만 허용합니다.
실무 적용 시나리오: PR 검토, 설계 리뷰, 코드 수정 시 과잉 설계 패턴 탐지와 억제에 도움을 줍니다.

Quick Start

Enable moyu-ko to enforce minimal edits and prevent unwanted refactors.

Frequently Asked Questions about moyu-ko

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

FAQPage Schema

How do I prevent overengineering and unnecessary refactoring during code review?▼

Preventing overengineering during code review requires an explicit-change policy that detects and suppresses overengineering patterns, ensuring only user-requested changes are applied. This blocks unwanted abstractions and enforces minimal edits.

What is an explicit-change policy for managing code edits?▼

An explicit-change policy for code edits is a guardrail mechanism that restricts modifications to user-requested changes only. It prompts for user confirmation before applying broader edits to prevent unnecessary documentation changes or refactors.

How to stop unwanted code abstractions and unrequested changes in PRs?▼

To stop unwanted code abstractions in PRs, enable guardrails that detect overengineering patterns and enforce minimal changes. This ensures only explicitly requested modifications pass through, prompting for confirmation before broader edits are applied.

Does enforcing minimal changes work for design reviews and code modifications?▼

Enforcing minimal changes works across design reviews, PRs, and code modifications. It applies guardrails during these workflows to identify overengineering patterns, suppress unnecessary refactors, and prompt for confirmation before broader edits.

When should I use guardrails to suppress overengineering patterns?▼

Use guardrails to suppress overengineering patterns when enforcing minimal edits during design reviews, PRs, or code modifications. They activate to prevent unnecessary refactors, abstractions, or documentation changes that were not explicitly requested.