# Skenklok AI Dev Utility Implementation Review Before Commit

> Implementation review before commit (simplicity + requirements)

- Skill: `tomevault-io/skenklok-ai-dev-utility-implementation-review-before-commit` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/skenklok-ai-dev-utility-implementation-review-before-commit`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/skenklok-ai-dev-utility-implementation-review-before-commit/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/skenklok-ai-dev-utility-implementation-review-before-commit

---


# Implementation review before commit (simplicity + requirements)

## Scope

- Staged diff is the source of truth.
- Optimize for: clarity, low cyclomatic complexity, maintainability, and meeting requirements.

## Default workflow

1. Collect staged diff + changed file list
   - `git diff --cached`
   - `git diff --cached --name-only`

2. Reconstruct intent
   - What requirement is being implemented or fixed?
   - What are the acceptance criteria implied by the diff?
   - State assumptions if requirements are not present.

3. Review for simplicity and patterns
   - Use the checklist in `reference/implementation-checklist.md` (load if needed).
   - Specifically check:
     - unnecessary abstraction, premature generalization
     - deeply nested conditionals (suggest guard clauses)
     - duplicated logic (extract small helpers)
     - error handling consistency
     - boundary validation (inputs, nulls, types)
     - performance footguns in hot paths
     - readability: naming, file organization, “one responsibility” per function

4. Requirement trace
   - For each inferred requirement, point to the code that fulfills it.
   - Call out gaps or “looks implemented but not actually enforced”.

5. Report
   - PASS / WARN / FAIL
   - “Meets requirements?” yes/no with evidence
   - Top 3 complexity reductions (smallest diffs)
   - Any risky patterns with safer alternatives

## Guardrails

- Default to minimal-change suggestions (small PR/commit friendliness).
- Don’t bikeshed style; focus on correctness, simplicity, and requirements.
- Don’t claim compliance with a requirement unless the diff shows it.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/skenklok) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-15 -->