kiss

Reviews code for over-engineering, pattern drift, failure surfaces, dead weight, and bugs.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/inayayousfi/myconfig --skill kiss-inayayousfi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kiss
Source: https://github.com/inayayousfi/myconfig/tree/main/dotfiles/ai/.agents/skills/kiss
Command: npx skills add https://github.com/inayayousfi/myconfig --skill kiss-inayayousfi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code that works can still be built wrong: over-abstracted, inconsistent with repository conventions, or carrying dead weight. This Skill performs a rigorous, design-first code review that judges structure and maintainability before hunting for bugs, so reviews produce evidence-backed findings instead of taste-based opinions. ## Core Features & Use Cases - Design-first review: Builds a counterfactual of the smallest credible shape before line-level review, so every structural finding names the concrete machinery it removes. - Six structured checks: Over-engineering, pattern drift, failure surface, naive edge cases, dead weight, and bugs, each with explicit scoping rules to avoid duplicated findings. - Confidence and cross-verification: Every finding gets a LOW/MEDIUM/HIGH confidence tag, with non-HIGH findings verified by a fresh subagent and empirical checks (tests, repros) where possible. - Use Case: After implementing a feature branch, ask for a review of the diff against the fork point; the Skill derives the target from git state, compares conventions against similar modules, and reports a copy-pasteable markdown review without modifying any code. ## Quick Start Ask the assistant to review the current branch changes using the kiss skill and report design findings with confidence tags.

Frequently Asked Questions about kiss

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

FAQPage Schema
How do I review a feature branch for over-engineering?▼

Name the branch or let the Skill derive the target: off the default branch it computes the real fork point with git merge-base and reviews that diff. It builds a smallest-credible-shape counterfactual first, then reports structural findings with the concrete machinery each one removes.

What does a design-first code review check?▼

It runs six checks: over-engineering, pattern drift, failure surface, naive edge cases, dead weight, and bugs. Design checks run against a counterfactual before correctness, and each finding includes file:line, evidence from repository conventions, a directional fix, and a confidence tag.

Can the review target uncommitted or staged changes?▼

Yes, but the caller must name the exact paths for staged, unstaged, or untracked changes. Committed changes default to the latest commit, and on the default branch the whole repository is reviewed in one pass.

Does the code review skill fix the issues it finds?▼

No. The Skill never modifies code, even for critical bugs. It reports findings in plain markdown and offers the fix to whoever requested the review, letting them decide whether to proceed.

How are uncertain review findings handled?▼

Every finding gets a LOW, MEDIUM, or HIGH confidence tag. Anything below HIGH is cross-verified by a fresh subagent with no category hints, and findings are upgraded or downgraded based on agreement but never silently dropped.