seniordev-review

Reviews code diffs for over-engineering and lists what to delete or simplify.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/kellymears/agents --skill seniordev-review-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seniordev-review
Source: https://github.com/kellymears/agents/tree/main/plugins/seniordev/skills/seniordev-review
Command: npx skills add https://github.com/kellymears/agents --skill seniordev-review-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate unnecessary complexity: hand-rolled utilities that duplicate the standard library, speculative abstractions with a single implementation, and dependencies that replicate native platform features. This Skill reviews diffs exclusively for that over-engineering and tells you exactly what to cut. ## Core Features & Use Cases - Complexity-only review: Ignores correctness, security, and performance to focus solely on finding code that can be deleted or shrunk. - Tagged one-line findings: Each finding uses a tag (delete:, stdlib:, native:, yagni:, shrink:) with the location, what to cut, and what replaces it. - Net-lines scoring: Ends every review with a net: -<N> lines possible metric, or Lean already. Ship. when nothing can be cut. - Use Case: After writing a feature branch, ask for an over-engineering review to discover that your 27-line email validator class can be replaced by a single "@" in email check before merging. ## Quick Start Ask the assistant to review this diff for over-engineering and tell me what can be deleted.

Frequently Asked Questions about seniordev-review

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

FAQPage Schema
How do I review code for over-engineering?▼

Invoke the review on a diff and it returns one line per finding: location, a tag like stdlib, native, yagni, delete, or shrink, what to cut, and what replaces it. It ends with a net count of lines that can be removed.

What kinds of complexity does an over-engineering review find?▼

It finds hand-rolled code the standard library already ships, dependencies duplicating native platform features, abstractions with only one implementation, unused configuration, and logic that can be expressed in fewer lines.

Does this review catch bugs and security issues?▼

No. It deliberately excludes correctness bugs, security holes, and performance problems, which belong in a normal review pass. This review only hunts unnecessary complexity and complements a standard correctness-focused review.

Will the review apply the suggested deletions automatically?▼

No. It only lists findings with locations and replacements; it does not modify the code. You decide which suggestions to apply and make the edits yourself or in a follow-up step.

When should I not use an over-engineering review?▼

Avoid it when you need correctness, security, or performance feedback, since those are explicitly out of scope. It also never flags minimal tests or assert-based self-checks, so do not expect test coverage analysis.