hos-silly-mock-001

Detect unannotated mock data, regex abuse, and silent failures in generated code.

12|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/lxcxjxhx/HOS_SKILL_WORKFLOW --skill hos-silly-mock-001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hos-silly-mock-001
Source: https://github.com/lxcxjxhx/HOS_SKILL_WORKFLOW/tree/main/04-HOS-Silly-Mock
Command: npx skills add https://github.com/lxcxjxhx/HOS_SKILL_WORKFLOW --skill hos-silly-mock-001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-generated code often includes unannotated mock data, regex abuse for structured data parsing, and silent failure patterns that create fake, seemingly functional systems with no real data bindings or error handling, leading to unmaintainable production code.

Core Features & Use Cases

  • 4-Layer Enforcement Engine: Detects mock data leakage, regex abuse for JSON/HTML/XML/CSV parsing, unbound data variables, and silent failure patterns in generated code.
  • Reality Scoring: Generates a 0-100 reality score with configurable thresholds for development, pre-production, and production environments, plus CI/CD quality gate integration.
  • Use Cases: AI code generation self-checks, code review for mock data leakage, pre-commit hook validation, and CI/CD pipeline quality gates for TypeScript, JavaScript, and other language codebases.

Quick Start

Use the hos-silly-mock-001 skill to analyze your project's source code for fake data patterns, regex abuse, and silent failures, then review the generated reality score and prioritized fix recommendations to improve code authenticity.

Frequently Asked Questions about hos-silly-mock-001

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

FAQPage Schema
How do I detect unannotated mock data in AI generated TypeScript code?

Detect unannotated mock data in AI generated TypeScript by applying static analysis to enforce explicit mock annotations and verify source-transform-sink data binding. The engine outputs a reality score indicating code authenticity.

Why does using regex for JSON parsing create silent failure patterns in my codebase?

Regex for JSON parsing creates silent failure patterns by bypassing structural validation and error handling, resulting in unbound data variables. Detecting this regex abuse requires static analysis enforcing standard parsers to guarantee complete data binding.

Can I use static analysis reality scoring as a CI/CD quality gate for JavaScript code?

Yes, reality scoring functions as a CI/CD quality gate for JavaScript. The engine generates a 0-100 score with configurable thresholds for development, pre-production, and production environments to block unmaintainable code from deployment.

What is a reality score threshold in AI code generation quality checks?

A reality score threshold is a configurable 0-100 metric evaluating AI code authenticity in quality checks. It measures explicit mock data annotations, standard parser usage, and complete data binding to detect fake, non-functional systems.

Does mock data detection work without adding explicit annotations to my existing code?

Mock data detection works by identifying unannotated mock data patterns, explicitly flagging code lacking proper annotations. It enforces explicit mock data annotations to verify source-transform-sink data binding and prevent fake systems.

What are the limitations of static analysis for preventing silent failure patterns in production?

A limitation of static analysis for preventing silent failure patterns is its reliance on enforcing source-transform-sink data binding and standard parser usage without runtime execution. It generates a reality score to gate code but cannot catch dynamic execution errors.