critical-bug-detector

Verify VoiceLite release packages for file presence, hashes, and version consistency.

12|3|Updated Sep 24, 2025
One-click install
npx skills add https://github.com/mikha08-rgb/VoiceLite --skill critical-bug-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critical-bug-detector
Source: https://github.com/mikha08-rgb/VoiceLite/tree/main/.claude/skills/critical-bug-detector
Command: npx skills add https://github.com/mikha08-rgb/VoiceLite --skill critical-bug-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents catastrophic release failures by automatically verifying critical files, version consistency, and build configurations, ensuring a stable and reliable product for users.

Core Features & Use Cases

  • Model Verification: Ensures the Whisper AI model (ggml-tiny.bin) and whisper.exe are correctly bundled and not ignored by Git.
  • Version Consistency: Checks that version numbers match across .csproj, .iss, and package.json files.
  • Build Configuration: Verifies the installer is built in Release mode and logging is enabled.
  • Use Case: Before deploying a new version of VoiceLite, use this skill to automatically run a comprehensive checklist, catching a missing AI model or a version mismatch that could otherwise lead to a broken release and frustrated users.

Quick Start

Run a critical pre-release check for VoiceLite version 1.0.97, focusing on model file integrity and version consistency.

Frequently Asked Questions about critical-bug-detector

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

FAQPage Schema
How do I prevent critical bugs before releasing software?

Pre-release checks automate verification of files, versions, and build configurations before deployment. This Skill runs comprehensive checks on release packaging—verifying model files, executable integrity, version consistency across project files, and build mode settings—to catch breaking issues before users encounter them.

How do I verify version consistency across .csproj, .iss, and package.json files?

Version consistency checks compare version numbers declared in .csproj, .iss installer configuration, and package.json files simultaneously. This Skill enforces matching versions across all three to prevent deployment with misaligned version strings that confuse users and break installation workflows.

Can I automate checks for missing model files and executables in my installer build?

Yes. This Skill verifies that required model files like ggml-tiny.bin and executables like whisper.exe are present, properly sized, not Git-ignored, and have valid hash integrity before packaging. It runs during installer builds and configuration changes to catch missing dependencies early.

What should I check before deploying a new software release?

Pre-release checks should verify file presence and integrity, executable hashes, version consistency across configuration files, build mode set to Release, required dependencies included, and Git state. This Skill performs all these checks automatically, preventing broken or incomplete releases from reaching users.

Why would my installer fail after release if I skip pre-release validation?

Missing model files, version mismatches, or incorrect build modes can cause installers to fail silently or produce broken executables in production. Pre-release validation catches these issues before deployment, avoiding customer-facing failures and support burden from broken releases.