sanity-check

Name: sanity-check
Availability: InStock
Author: vinaykumarvk

Automate code build, test, and regression verification across review domains.

1|1|Updated Nov 13, 2025

Search Tags:#regression testing #code validation #automated review #build verification #code conflicts

Ready to run

npx skills add https://github.com/vinaykumarvk/PS-WMS --skill sanity-check-vinaykumarvk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sanity-check
Source: https://github.com/vinaykumarvk/PS-WMS/tree/main/.claude/skills/sanity-check
Command: npx skills add https://github.com/vinaykumarvk/PS-WMS --skill sanity-check-vinaykumarvk

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams verify the integrity of code builds and tests after implementing parallel fixes, preventing regressions and conflicts.

Core Features & Use Cases

Regression Detection: Automates checks for build failures, test failures, and code conflicts in a monorepo environment.
Workflow Validation: Validates that critical review findings such as merge conflicts, broken imports, and design inconsistencies are addressed.
Use Case: After applying multiple code reviews across UI, security, and infra domains, use this Skill to automatically confirm that all systems are stable and ready for deployment.

Quick Start

Run this skill after you have completed code fixes and want to verify the stability of your repository to confirm everything is ready for release.

Frequently Asked Questions about sanity-check

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

FAQPage Schema

How do I verify build stability after applying multiple code reviews?▼

To verify build stability after code reviews, you can automate comprehensive verification of builds, tests, and regressions across multiple domains to ensure code stability and prevent deployment of regressions.

What is automated regression detection in a monorepo environment?▼

Automated regression detection in a monorepo environment checks for build failures, test failures, and code conflicts after parallel fixes are implemented to ensure overall repository integrity.

How do I validate that critical code review findings have been addressed?▼

You validate addressed code review findings by running automated workflow validation that confirms merge conflicts, broken imports, and design inconsistencies are resolved before release.

Can I check for code conflicts across UI, security, and infrastructure domains?▼

Yes, you can check for code conflicts across UI, security, and infrastructure domains by running a verification process that confirms all applied fixes leave systems stable and ready for deployment.

When do I need to run automated build verification?▼

You need to run automated build verification after you have completed code fixes and want to confirm repository stability, ensuring everything is ready for release without introducing regressions.

What are the limitations of automated code validation for post-review stability?▼

Automated code validation for post-review stability focuses strictly on builds, tests, and regressions, meaning it should be run after fixes are applied rather than during active development to prevent false conflicts.