code-review

Name: code-review
Availability: InStock
Author: Tien

Verify test results and scout edge cases during code reviews.

Updated Feb 25, 2025

Search Tags:#testing #software engineering #quality assurance #code review #verification #edge case detection

Ready to run

npx skills add https://github.com/VuNguyenVietTien/task-scheduler --skill code-review-vunguyenviettien

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/VuNguyenVietTien/task-scheduler/tree/main/.opencode/skills/code-review
Command: npx skills add https://github.com/VuNguyenVietTien/task-scheduler --skill code-review-vunguyenviettien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers perform structured, evidence-based code reviews to improve code quality and verify implementation claims efficiently.

Core Features & Use Cases

Technical Rigor: Facilitates reviewing code with emphasis on correctness, edge cases, and verification protocols.
Feedback Handling: Guides responses to review comments, ensuring clarity and technical integrity.
Edge Case Scouting: Identifies potential issues proactively before code review.
Use Case: Before merging a new feature branch, use this Skill to verify test results, review code adherence to standards, and scout for hidden edge cases that might cause future bugs.

Quick Start

Invoke this skill to evaluate the latest code changes for potential issues before submitting a pull request.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I perform an evidence-based code review before merging a feature branch?▼

An evidence-based code review verifies test results and implementation claims while scouting for edge cases. This process ensures high reliability and correctness before merging new code branches by guiding structured feedback interactions.

What is edge case scouting in software engineering and when do I need it?▼

Edge case scouting in software engineering proactively identifies potential hidden issues that might cause future bugs. You need this verification process before submitting a pull request to ensure your implementation handles unexpected scenarios correctly.

How do I verify test results and check code adherence to standards?▼

To verify test results and check code adherence to standards, evaluate the latest code changes against correctness protocols. This structured review emphasizes technical rigor to confirm the implementation matches the claimed behavior and quality standards.

Can I use automated code review to guide responses to review comments?▼

Yes, automated code review can guide responses to review comments by ensuring clarity and technical integrity. It facilitates feedback handling interactions to maintain technical rigor and evidence-based verification throughout the development workflow.

What is the best way to scout for hidden edge cases that might cause future bugs?▼

The best way to scout for hidden edge cases is through comprehensive code evaluation that emphasizes correctness and verification protocols. This proactive approach identifies potential issues before the formal code review process begins.

Why does my code review process lack technical rigor and miss hidden bugs?▼

Your code review lacks technical rigor if it skips verifying test results or scouting for edge cases. Implementing structured, evidence-based evaluation ensures correctness and proactively identifies hidden bugs before merging.