ego-check

Analyze code diffs for premature abstraction and unnecessary cleverness.

6|Updated Jan 14, 2026

Search Tags:#code review #refactoring #software design #maintainability #engineering culture

Ready to run

npx skills add https://github.com/markacianfrani/armor --skill ego-check-markacianfrani

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ego-check
Source: https://github.com/markacianfrani/armor/tree/main/skills/ego-check
Command: npx skills add https://github.com/markacianfrani/armor --skill ego-check-markacianfrani

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the tendency for developers to prioritize cleverness and personal expression over maintainability, helping to identify over-engineered or ego-driven code that hinders team collaboration.

Core Features & Use Cases

Code Review Lens: Evaluates diffs for signs of premature abstraction, fashion-driven patterns, and unnecessary indirection.
Human-Centric Reframing: Encourages writing code that is kind to the next maintainer by prioritizing simplicity and readability.
Use Case: Use this during a pull request review to identify if a complex one-liner or a new, trendy framework is actually serving the project or just the author's self-image.

Quick Start

Ask the ego-check skill to review the current diff for signs of over-engineering and suggest simpler alternatives.

Frequently Asked Questions about ego-check

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

FAQPage Schema

How do I review a code diff for over-engineering and unnecessary cleverness?▼

Reviewing code for over-engineering involves analyzing diffs to identify ego-driven design choices like premature abstraction and unnecessary cleverness. This flags author-serving complexity and suggests simpler, more readable alternatives that prioritize team maintainability.

What is ego-driven code and how does it affect software maintainability?▼

Ego-driven code prioritizes developer cleverness and personal expression over maintainability, often using premature abstractions or trendy patterns. It hinders team collaboration by creating unnecessary indirection and complex structures that are difficult for the next maintainer to read and update.

How do I check a pull request for premature abstraction and fashion-driven patterns?▼

Checking a pull request for premature abstraction involves evaluating the diff for unnecessary indirection and fashion-driven patterns. This identifies whether complex one-liners or trendy frameworks actually serve the project's needs or just satisfy the author's self-image, ensuring humane code structures.

When should I refactor code for empathy and team-oriented clarity?▼

You should refactor code for empathy and team-oriented clarity when reviews reveal over-engineered structures hindering collaboration. Prioritize simplicity and readability to ensure the code is kind to the next maintainer rather than serving the original author's ego.

Does this code review approach work for identifying unnecessary indirection in any software design?▼

Yes, this code review approach works for any software design by analyzing diffs to identify author-serving indirection. It specifically flags unnecessary cleverness and premature abstraction, ensuring the codebase remains maintainable and prioritizes human-centric readability.