fresh-eyes_skill

Overview

This skill re-reads code you just wrote or modified with a fresh perspective to catch obvious bugs, errors, and risky patterns. Use it immediately after finishing a feature, fixing a bug, or making any code changes to prevent simple mistakes from slipping into commits. It focuses strictly on correctness problems, not style or refactors.

How this skill works

Identify files changed in the current session (for example, via git diffs) and read each file as if seeing it for the first time. Look specifically for logic errors, typos, missing checks, race conditions, off-by-one mistakes, and missing cleanup or error handling. For each problem found, explain the issue in one sentence and fix it immediately, then produce a short summary of fixes or a clean bill of health.

When to use it

• After completing a feature or a bug fix before committing
• When you feel something subtle might be off after a long coding session
• Before pushing changes to a shared branch
• When adding or modifying async logic or resource handling
• As a final pass on boundary conditions and input validation

Best practices

• Limit scope to modified files only—don’t refactor working code
• Prefer short, concrete fixes: one-line explanations and immediate edits
• Prioritize correctness issues: missing checks, returns, awaits, and cleanup
• Use git diff to reliably identify changed files before reviewing
• Avoid adding new features, style changes, or large reorganizations

Example use cases

• You finished a pagination feature—check for off-by-one and boundary logic
• You fixed a crash—verify null/undefined checks and proper error propagation
• You changed async code—ensure all necessary awaits and cleanup run
• You updated a data transformation—catch copy/paste or incorrect variable use
• You prepared a hotfix—confirm no missing returns or resource leaks