code-review-correctness-finder-angles

Name: code-review-correctness-finder-angles
Availability: InStock
Author: mkusaka

Analyze diff files for line-by-line correctness and cross-file dependencies.

7|Updated Mar 8, 2026

Search Tags:#code quality #diff analysis #software engineering #code review #error detection #cross-file tracing

Ready to run

npx skills add https://github.com/mkusaka/ccskills --skill code-review-correctness-finder-angles

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-correctness-finder-angles
Source: https://github.com/mkusaka/ccskills/tree/main/skills/code-review-correctness-finder-angles
Command: npx skills add https://github.com/mkusaka/ccskills --skill code-review-correctness-finder-angles

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenges of code reviews by providing a multi-faceted analysis of code changes, focusing on correctness, behavior, and inter-file dependencies.

Core Features & Use Cases

Line-by-Line Diff Scan: Inspects each line of code changes, checking for potential issues.
Removed-Behavior Audit: Identifies removed code that could impact functionality.
Cross-File Tracing: Monitors changes across different files to ensure compatibility.

Quick Start

Execute the code-review-correctness-finder-angles skill on your recent code changes to identify potential issues and maintain code quality.

Frequently Asked Questions about code-review-correctness-finder-angles

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

FAQPage Schema

How do I review code changes for correctness and cross-file dependencies?▼

Code review for correctness involves inspecting diff files line-by-line to identify potential issues, auditing removed code for behavior impacts, and tracing cross-file dependencies to ensure compatibility. This maintains code integrity during reviews.

What is cross-file tracing in code review and when do I need it?▼

Cross-file tracing monitors code changes across different files to ensure compatibility. It is needed during code reviews when modifications in one file may impact functionality or dependencies in other files within the software project.

How do I detect removed code that could break functionality during a code review?▼

Detect removed code impacts by performing a removed-behavior audit on your diff files. This process inspects deleted lines to identify functionality changes that could break existing behavior before merging code changes.

Does line-by-line diff analysis work for finding errors in multi-file software changes?▼

Line-by-line diff analysis inspects each line of code changes for potential issues. It works for multi-file changes by combining detailed line inspection with cross-file tracing to detect errors across dependencies.

What's the best way to streamline code reviews for error detection?▼

Streamlining code reviews for error detection requires multi-faceted analysis of diffs. Inspect line-by-line correctness, audit removed behavior, and trace cross-file dependencies to detect errors and maintain code quality efficiently.