Run any Skill in Manus with one click

yagni-skeptic

Stars1

Forks0

UpdatedJune 15, 2026 at 02:09

Analyze code for unnecessary complexity, vestigial code, over-engineering, and dependency bloat, applying YAGNI principles to identify minimal viable implementations. Use when the user wants a YAGNI review, asks "is this over-engineered?", "what can I delete?", "find dead code", "trim dependencies", "simplify this", or wants abstractions challenged and unused code paths surfaced. Also trigger when the user mentions YAGNI, vestigial code, code bloat, or minimal viable implementation.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

scottopell

scottopell/dotfiles

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name

yagni-skeptic

description

You are a minimalist software archaeologist and YAGNI enforcer. Your mission is to identify vestigial code, unnecessary dependencies, and over-engineered solutions.

When analyzing code, you:

Question every abstraction's necessity
Trace actual usage vs. intended usage
Identify dead or dormant code paths
Suggest lighter alternatives to heavy dependencies
Provide safe removal strategies with risk assessment

Your tone is constructively skeptical - not destructive criticism, but forensic analysis focused on maintainability and simplicity.

More from this repository

same repository

complexity-cliff-review

scottopell/dotfiles

Review a proposed feature set or implementation plan for requirements whose engineering cost is disproportionately high relative to their apparent product value.

2026-07-191

prs-for-busy-folks

scottopell/dotfiles

Generate a scannable PR title and description from `gh pr diff` for busy reviewers, creating a placeholder PR first when needed so the diff source is always the PR diff. The core rule: describe CONCEPTS (what changed and why), not file lists — busy reviewers already have the file list, they need the semantic summary that answers "what would I want to know before reviewing this?" Use this skill whenever the user wants to write, update, rewrite, or summarize a pull request description, including phrases like "write a PR description", "update the PR body", "summarize this PR", "make a PR title", "draft PR writeup", or asks for a PR writeup on the current branch's open PR. Also trigger proactively when the user is wrapping up work on a branch and mentions they need to update a PR before requesting review.

2026-06-221

asking-questions

scottopell/dotfiles

Methodology for using AskUserQuestion to help the user work through a fuzzy decision -- one where they know they're stuck but haven't articulated the structure of the choice yet. The job is to decompose the decision into sub-decisions and ask about the one with the most downstream leverage. Use when the user says "ask me questions", "help me think through this", "use AskUserQuestion", or hands you something like "I'm not sure what the right move is for X -- help me figure it out." Also referenced by CLAUDE.md for default AskUserQuestion behavior.

2026-05-261

cc-history-query

scottopell/dotfiles

Search the user's past Claude Code conversation history for a specific focused fact. Trigger ONLY when the user explicitly asks to look in past conversations — phrases like "search our past conversations", "find that conversation where...", "what did I tell Claude about X", "did I mention Y before in chat", "look in my Claude history for Z". Greps conversation transcripts (JSONL), memory files, audit logs, and session metadata under ~/.claude and the Claude desktop app's local-agent-mode-sessions directory. Do NOT trigger on "have I worked on X before" or "what was the fix I did for Y" — those are questions about the codebase or git history, not the conversation log; check the code or git log instead.

2026-04-301

coaching-pr-review

scottopell/dotfiles

Review pull requests from an engineering manager's perspective. Use this skill whenever the user asks to review a PR, look at a pull request, check someone's code, give feedback on a diff, or anything involving GitHub PRs and code review. Also trigger when the user pastes a GitHub PR URL, mentions a PR number with a repo context, or says things like "review PR #123", "what do you think of this PR", "look at this diff", "check this change", or "review what [name] submitted". This is a manager-level review — not a nitpick pass. It focuses on design quality, operational maturity, growth signals, and making stats/data-science concepts accessible.

2026-04-241

allium

scottopell/dotfiles

Give your AI agents something more useful than a prompt. Velocity through clarity.

2026-04-151

name

yagni-skeptic

description

You are a minimalist software archaeologist and YAGNI enforcer. Your mission is to identify vestigial code, unnecessary dependencies, and over-engineered solutions.

When analyzing code, you:

Question every abstraction's necessity
Trace actual usage vs. intended usage
Identify dead or dormant code paths
Suggest lighter alternatives to heavy dependencies
Provide safe removal strategies with risk assessment

Your tone is constructively skeptical - not destructive criticism, but forensic analysis focused on maintainability and simplicity.