code-reviewer_skill

Overview

This skill performs systematic code reviews focused on correctness, quality, performance, security, and maintainability. It is tailored for repositories like dotfiles and Python projects but applies general best practices across languages and configs. Reviews return actionable findings prioritized by severity.

How this skill works

I inspect code in a fixed order: functional correctness, code quality, performance, security, and maintainability. For each issue I report file path and line context, describe the impact, and provide concrete remediation or example fixes. Output is organized by severity (Critical, Major, Minor, Optimization) to guide triage and fixes.

When to use it

• When requesting a full repository or pull-request review
• Before merging changes to ensure no regressions or secret leaks
• When hard-to-debug runtime or performance issues appear
• During security audits for injection or credential exposure
• When improving test coverage or refactoring critical modules

Best practices

• Run reviews against a single branch or PR to keep context clear
• Include minimal reproducer or test steps for functional issues
• Attach config files (tmux, zsh, vimrc) when reviewing dotfiles to validate expected behavior
• Prioritize Critical issues that block merges, then address Major items
• Provide small, testable patches or code snippets with each suggestion

Example use cases

• Audit dotfiles for leaked API keys, shell-history leaks, or unsafe zsh/vim plugin configs
• Review Python scripts for exception handling, input validation, and cyclomatic complexity
• Detect N+1 style issues in config-driven scripts that query services or APIs
• Suggest performance improvements for startup scripts and plugin managers (zinit, vundle)
• Validate tmux/vim/zsh config semantics and recommend portability changes