Runtime Patch Review

Run node --check and regex scans on JavaScript and HTML runtime patches.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/skerishKang/LoveBud --skill runtime-patch-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Runtime Patch Review
Source: https://github.com/skerishKang/LoveBud/tree/main/skills/runtime-patch-review
Command: npx skills add https://github.com/skerishKang/LoveBud --skill runtime-patch-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It provides a fast, repeatable review of runtime patches and recent deployments by automating syntax checks, pattern scans, and HTML link verification to catch regressions and leftover debug artifacts before merging or shipping.

Core Features & Use Cases

  • Syntax and runtime checks: run node --check across changed JavaScript and serverless function files to detect syntax and immediate runtime issues.
  • Pattern and hygiene scanning: find duplicate event listeners, leftover console.* calls, TODO/FIXME/HACK markers, and discouraged casts like "as any".
  • HTML reference validation: discover external and internal broken links and verify JS/CSS asset references.
  • Use Case: After a patch deploy or before merging a PR, run this review to validate changed *.js and *.html files and produce a checklist-style review summary for reviewers.

Quick Start

Run a patch review for files changed in the last commit and generate a checklist-style review summary highlighting syntax errors, duplicate patterns, and broken links.

Frequently Asked Questions about Runtime Patch Review

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

FAQPage Schema
How do I automate post-deploy patch review for JavaScript and HTML files?

Post-deploy patch review automates syntax checks, regex pattern scans, and HTML link validation across changed JavaScript and HTML files. It generates a checklist-style summary to catch regressions and leftover debug artifacts before merging or shipping.

What is the best way to check for duplicate event listeners and leftover console statements before merging?

Checking for duplicate event listeners and leftover console statements is handled by pattern and hygiene scanning. This process applies regex scans to identify anti-patterns, debug artifacts, and discouraged casts like "as any" in your codebase.

How do I validate broken HTML references and asset links during deploy verification?

Validating broken HTML references involves discovering external and internal links alongside verifying JS and CSS asset references. This ensures web MVP repositories maintain correct resource paths during pre-merge validation scenarios.

Can I run syntax checks on serverless function files without deploying them?

Yes, you can run syntax checks on serverless function files without deploying by executing node --check. This detects immediate syntax and runtime issues across changed JavaScript files during the patch review process.

Does runtime patch review work with files changed in the last commit only?

Runtime patch review targets files changed in the last commit to perform targeted validation. It runs node --check, scans for duplicate patterns, and verifies links to produce a focused checklist-style review summary for reviewers.

What are the limitations of regex-based pattern scanning for code review?

Regex-based pattern scanning limitations include relying on predefined anti-pattern matching rather than deep semantic analysis. It identifies specific markers like TODO, FIXME, and HACK comments but may miss complex logical regressions in JavaScript files.