check

Review code changes and projects for quality, security, and release readiness.

14|Updated May 27, 2026
One-click install
npx skills add https://github.com/mlhiter/skills --skill check-mlhiter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check
Source: https://github.com/mlhiter/skills/tree/main/skills/check
Command: npx skills add https://github.com/mlhiter/skills --skill check-mlhiter

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines code reviews, project audits, and release processes, helping teams maintain high code quality and project integrity.

Core Features & Use Cases

  • Automated Code Review: Perform thorough code reviews with functional acceptance, adversarial review, and release-readiness gates.
  • Project Audit: Conduct project-wide code-quality assessments with a comprehensive rubric.
  • Release Worthiness Analysis: Evaluate the readiness of a project for release.

Quick Start

Run the "check" skill to review the latest changes to your project.

Frequently Asked Questions about check

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

FAQPage Schema
How do I automate code review for release readiness in my software development workflow?

Automated code review for release readiness validates your latest changes by applying functional acceptance, adversarial review, and release-readiness gates to ensure software quality. It requires Git and project documentation to evaluate code changes and project health.

What is a project audit and how does it assess code quality?

A project audit is a comprehensive code-quality assessment that evaluates project-wide integrity using a predefined rubric. It reviews code changes and project health to determine overall software quality and readiness for release.

How do I check if my project is ready for release?

To check release readiness, you run a release worthiness analysis that evaluates your project against functional acceptance criteria, adversarial review gates, and comprehensive project audit rubrics to validate code changes.

Do I need Git to perform a project audit and review code changes?

Yes, Git is required to perform project audits and review code changes. The process validates code changes and project health by analyzing Git history alongside your existing project documentation.

What is the best way to run an adversarial review on recent code changes?

The best way to run an adversarial review is to execute an automated review skill that applies release-readiness gates and functional acceptance checks to your latest Git changes, ensuring software quality and project integrity.

What are the limitations of automated code review for project audits?

Automated code review for project audits is limited by its reliance on Git and project documentation; without comprehensive project docs, the tool cannot fully validate code changes or accurately assess release readiness.