moyu-ja

Detect and suppress overengineering patterns in code reviews and PR workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Overengineering patterns are detected and automatically suppressed to keep code simple and maintainable, avoiding unnecessary rewrites and complexity.

Core Features & Use Cases

  • Automatic detection of overengineering patterns in codebases, reviews, and PRs.
  • Non-destructive guidance to remove unnecessary abstractions, extra classes, and dependencies.
  • Use-case: During code reviews, the skill flags overly complex changes and suggests minimal alternatives.

Quick Start

Analyze your codebase for overengineering patterns and apply the minimal, targeted fixes.

Frequently Asked Questions about moyu-ja

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

FAQPage Schema
How do I identify overengineering patterns during a code review?

To identify overengineering patterns during a code review, analyze PRs to detect and flag risky design patterns, unnecessary abstractions, and extra dependencies, enforcing minimal targeted changes within your defined scope.

What is the best way to prevent unnecessary abstractions in refactoring?

The best way to prevent unnecessary abstractions in refactoring is to enforce minimal, targeted fixes that suppress overengineering patterns, ensuring code simplicity and avoiding destructive rewrites of existing logic.

Can I use this to flag risky design patterns in pull requests?

Yes, you can use this to flag risky design patterns in pull requests by applying non-destructive guidance that detects overly complex changes and suggests minimal alternatives to maintain code simplicity.

How do I apply minimal changes to suppress overengineering in my codebase?

To apply minimal changes and suppress overengineering, analyze your codebase to detect unnecessary classes and dependencies, then apply targeted fixes to remove them without causing destructive rewrites.

When should I avoid adding extra dependencies to keep code simple?

You should avoid adding extra dependencies when an automated review detects overengineering patterns, enforcing code simplicity by suggesting minimal alternatives instead of introducing unnecessary complexity.