Dotfiles-nix simplify

Review changed code for reuse, quality, and efficiency, then fix any issues found. Use after completing an implementation to catch redundancy, dead code, and over-engineering before committing.

install

source · Clone the upstream repo

git clone https://github.com/not-matthias/dotfiles-nix

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/not-matthias/dotfiles-nix "$T" && mkdir -p ~/.claude/skills && cp -r "$T/modules/home/programs/cli-agents/shared/skills/simplify" ~/.claude/skills/not-matthias-dotfiles-nix-simplify && rm -rf "$T"

manifest: modules/home/programs/cli-agents/shared/skills/simplify/SKILL.md

source content

Simplify

Review your implementation before stopping. Run through each check below and fix issues in-place.

Checklist

Simpler approach? Is there a more straightforward way to achieve the same result? Fewer moving parts, less indirection, fewer abstractions.
Redundant code? Are there duplicated blocks, near-identical functions, or copy-pasted logic that should be consolidated?
Duplicate logic? Did you introduce something that already exists elsewhere in the codebase? Check for existing helpers, utilities, or patterns before adding new ones.
Dead code? Are there unused imports, variables, functions, or commented-out blocks that should be removed?
Over-engineering? Did you add abstractions, configurability, error handling, or future-proofing that isn't needed for the current task? Three similar lines of code is better than a premature abstraction. Do not remove helpful abstractions that improve organization and maintainability.
Clarity over brevity? Prefer explicit, debuggable code over dense one-liners.
Readable conditionals? Avoid nested ternaries when they hurt readability; use clearer conditionals.
Tests still pass? If the project has tests, run them. If any fail due to your changes, fix them before finishing.

Rules

Preserve functionality: never change behavior; only simplify structure and readability.
Only review files that were changed in this session or are staged in git.
Fix issues directly — don't just report them.
Only flag high-confidence issues. False positives are worse than missed nits.
If no issues are found, briefly confirm the implementation is clean (one sentence).
Do NOT add comments, docstrings, or type annotations that weren't there before.
Do NOT refactor surrounding code that wasn't part of the original change.