self-review-changes

Analyze latest repository code changes for accuracy, integration, and best practices.

Updated May 2, 2020
One-click install
npx skills add https://github.com/vankichi/dotfiles --skill self-review-changes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-review-changes
Source: https://github.com/vankichi/dotfiles/tree/main/claude/ja/skills/self-review-changes
Command: npx skills add https://github.com/vankichi/dotfiles --skill self-review-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a comprehensive review of code changes to ensure quality, integrity, and adherence to best practices.

Core Features & Use Cases

  • Code Review Analysis: Conducts a thorough self-review of code changes for accuracy, integration, and best practice adherence.
  • Four-Phase Process: Mindset shift, observation, analysis, and action phases for a structured review process.
  • Use Case: Before merging a code change, use this Skill to ensure all changes align with established best practices and do not introduce new issues.

Quick Start

Execute the 'self-review-changes' skill to initiate the comprehensive self-review process for your latest code changes.

Frequently Asked Questions about self-review-changes

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

FAQPage Schema
How do I self-review code changes before merging to ensure best practices?

To self-review code changes before merging, you can analyze the latest repository updates for accuracy, integration, and best practice adherence to identify potential issues like code drift.

What is code drift and how does a code review analysis detect it?

Code drift occurs when implementation diverges from specifications. A comprehensive code review analysis detects this by identifying inconsistencies between the established specifications and the actual code changes.

How do I check my latest code changes for improper usage of sentinel values?

You can check latest code changes for improper sentinel value usage by running a structured self-review analysis that observes and flags potential issues affecting code integrity and accuracy.

What is the best way to structure a code review for accuracy and integration?

The best way to structure a code review for accuracy and integration is using a four-phase process: mindset shift, observation, analysis, and action phases to systematically evaluate changes.

Can I use a self-review process to find inconsistencies between specifications and implementation?

Yes, you can use a comprehensive self-review process to find inconsistencies between specifications and implementation by analyzing the latest code changes for adherence to established best practices.

When do I need a comprehensive code review analysis for my repository?

You need a comprehensive code review analysis for your repository before merging code changes to ensure all updates align with best practices and do not introduce new issues.