mo-self-review

Automates code review and self-assessment for MatrixOne git working trees.

1.9k|305|Updated Feb 18, 2021

Search Tags:#code quality #git #code review #self-assessment #MatrixOne

Ready to run

npx skills add https://github.com/matrixorigin/matrixone --skill mo-self-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mo-self-review
Source: https://github.com/matrixorigin/matrixone/tree/main/.agents/skills/mo-self-review
Command: npx skills add https://github.com/matrixorigin/matrixone --skill mo-self-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires unhappy-path-audit, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of code review and self-assessment for MatrixOne changes, ensuring a thorough and systematic analysis before pushing or opening a pull request.

Core Features & Use Cases

Automated Code Review: Provides a multi-angle, first-principles review of code changes.
Functional Closure Investigation: Ensures complete functional closure of each change.
Unhappy-Path Coverage: Checks for potential issues in error handling and resource management.
Compatibility and Boundary Testing: Ensures backward compatibility and boundary conditions are handled correctly.
Use Case: Before pushing code changes to a MatrixOne repository, use this Skill to automatically perform a comprehensive review and self-assessment.

Quick Start

Run the mo-self-review skill on your working diff before pushing: /mo-self-review

Frequently Asked Questions about mo-self-review

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

FAQPage Schema

How do I automate code review and self-assessment for MatrixOne changes before pushing?▼

To automate code review for MatrixOne changes, run the mo-self-review skill on your git working tree diff against the base branch. It executes a multi-angle, first-principles review covering functional closure, compatibility, and boundary testing before you open a pull request.

What does a comprehensive code self-assessment check for in a git diff?▼

A comprehensive code self-assessment checks the git diff for functional closure verification, unhappy-path coverage in error handling, resource management issues, backward compatibility, and boundary condition handling to ensure code quality before submission.

Do I need a specific git working tree state to perform a MatrixOne code review?▼

Yes, you need a git working tree with an active diff against the base branch to perform a MatrixOne code review. The skill analyzes the uncommitted or staged changes to provide automated multi-angle feedback and self-assessment.

How do I check unhappy-path coverage and error handling in my code changes?▼

To check unhappy-path coverage and error handling in your code changes, use the mo-self-review skill which integrates the unhappy-path-audit dependency. It systematically investigates potential issues in resource management and error paths within your current diff.

Can I verify backward compatibility and boundary conditions for MatrixOne code changes automatically?▼

Yes, you can verify backward compatibility and boundary conditions automatically by running the mo-self-review skill. It assesses your MatrixOne code changes against boundary conditions to ensure existing functionality remains intact and edge cases are handled correctly.