quick-check

Run build and test scripts, check handlers, and report git status.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/chriscarterux/Mothership --skill quick-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: quick-check
Source: https://github.com/chriscarterux/Mothership/tree/main/.claude/skills/quick-check
Command: npx skills add https://github.com/chriscarterux/Mothership --skill quick-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill quickly identifies common issues in codebases without performing deep analysis, saving developers time on initial validation.

Core Features & Use Cases

  • Handler Check: Detects empty or placeholder event handlers.
  • Build & Test Execution: Runs standard build and test commands if available.
  • Git Status: Reports the current state of the repository.
  • Use Case: Before committing code, run this Skill to catch obvious mistakes like uncommented debugging code or unhandled user interactions.

Quick Start

Run a fast sanity check on the current project.

Frequently Asked Questions about quick-check

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

FAQPage Schema
How do I run a sanity check on my codebase before committing?

A sanity check for continuous integration pipelines performs rapid validation by detecting empty event handlers, running build and test scripts, and reporting git status to catch obvious mistakes before code is committed.

How does detecting empty event handlers improve code quality?

Detecting empty event handlers improves code quality by identifying placeholder functions and unhandled user interactions early, preventing obvious mistakes from being merged into the main codebase during initial validation.

Do I need npm to run build and test scripts during a sanity check?

Yes, you need npm installed if a package.json is present. The sanity check executes standard build and test commands using npm to validate that the project compiles and tests pass successfully.

What is the best way to catch uncommented debugging code in a pre-commit check?

The best way to catch uncommented debugging code in a pre-commit check is to run a rapid sanity check that scans for common codebase issues and reports the current git status without performing deep analysis.

Does this sanity check tool perform deep static code analysis?

No, this sanity check tool does not perform deep static code analysis. It quickly identifies common issues like empty handlers and failing tests to save time on initial validation rather than providing comprehensive code review.