skills.rest
hachej
hachejCOMMUNITY
Explore all skills by this author →
GitHub

fresh-eyes

Review plans, diffs, and pull requests for overlooked mistakes and risks.

45|2|Updated Apr 24, 2026
Search Tags:#quality assurance#code review#debugging#pull request#validation#risk assessment
One-click install
npx skills add https://github.com/hachej/boring-ui --skill fresh-eyes-hachej
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fresh-eyes
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skills/fresh-eyes
Command: npx skills add https://github.com/hachej/boring-ui --skill fresh-eyes-hachej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the common issue of cognitive bias and oversight when reviewing one's own plans, code, or pull requests, ensuring that critical errors and risks are identified before implementation.

Core Features & Use Cases

  • Objective Review: Provides a read-only, independent assessment of plans, diffs, or PRs.
  • Risk Mitigation: Specifically scans for overlooked mistakes, omissions, and broken acceptance criteria.
  • Use Case: Before merging a complex feature branch, use this skill to perform a final, meticulous audit of the code and test coverage to ensure no edge cases were missed.

Quick Start

Ask the agent to perform a fresh eyes review on the current pull request or plan file.

Frequently Asked Questions about fresh-eyes

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

FAQPage Schema
How do I perform an independent code review on my own pull request?▼

An independent code review on a pull request requires a read-only assessment of diffs to identify overlooked mistakes and risks. You can use an automated reviewer to scan changes and verify acceptance criteria without modifying the codebase.

What is the best way to validate acceptance criteria before merging a complex feature branch?▼

Validating acceptance criteria before merging requires a meticulous audit of code changes and test coverage. An objective, read-only review scans for omissions and broken criteria to ensure no edge cases were missed during implementation.

How does an independent read-only review mitigate cognitive bias in software development?▼

An independent read-only review mitigates cognitive bias by applying evidence-based reporting to your plans and code. It scans for overlooked mistakes, omissions, and risks that you might miss when reviewing your own work.

Can I use an automated review tool to perform risk assessment on plan files and diffs?▼

Yes, you can perform risk assessment on plan files and diffs using an automated review tool. It provides a rigorous, independent audit to identify overlooked mistakes and verify material issues before implementation.

Does an independent code review modify my repository during the validation process?▼

No, an independent code review does not modify your repository during validation. It performs a read-only assessment of your diffs and pull requests, strictly adhering to evidence-based reporting to identify risks without altering code.

Related Skills

Explore More Software Engineering Skills→
haidonglethqbhaidonglethqb

code-review

Define code-review scope and trigger verification steps across impacted files.

Community
Advanced
dmae97dmae97
130

omk-flow-pr-review

Inspect pull request diffs and generate merge recommendations with risk classification.

Community
Intermediate
adriaanmostert1976-labadriaanmostert1976-lab

quality-check

Analyze software requirements and failure modes to create test strategies and plans.

Community
Advanced
CaptainCrouton89CaptainCrouton89
497

Testing Code

Automate software tests to verify functionality against acceptance criteria.

Community
Basic