javascript-reviewer

name	javascript-reviewer
description	Review modern JavaScript for async behavior, modules, runtime correctness, security, tests, and performance.
version	1.0.0
since	2026-08-29
last_modified	2026-08-29
authors	["platform-engineering"]
stability	stable
min_platform_version	{"codex":"unknown","amazon-q":"unknown","antigravity":"unknown","auggie":"unknown","bob":"unknown","claude-code":"unknown","cline":"unknown","codebuddy":"unknown","continue":"unknown","costrict":"unknown","crush":"unknown","github-copilot":"unknown","gitlab-duo":"unknown","factory":"unknown","forgecode":"unknown","opencode":"unknown","openhands":"unknown","cursor":"unknown","roo-code":"unknown","kiro":"unknown","junie":"unknown","gemini-cli":"unknown","iflow":"unknown","kilocode":"unknown","kimi":"unknown","lingma":"unknown","pi":"unknown","qoder":"unknown","qwen":"unknown","windsurf":"unknown","ollama":"unknown"}
deprecated_since	null
replaces	null
supersedes	[]
changelog	[{"version":"1.0.0","date":"2026-08-29","change":"Initial generated production-ready SDLC / DevSecOps skill"}]

Javascript Reviewer

Purpose

Review modern JavaScript for ES2022 and later idiomatic usage, async and Promise correctness, module system consistency, event loop and microtask awareness, prototype chain and closure correctness, and runtime performance patterns. Treat regulatory, security, and operational references as review and evidence guidance, not legal advice.

Goal and behavioral contract

The authoritative Goal and artifact references are defined in descriptor.yaml. Capability boundaries, identity and delegation requirements, tool permissions, data boundaries, invariants, approval requirements, output contract, and operational limits are defined in contract.yaml. MCP/A2A trust boundaries and the reviewed execution closure live in integrations/ and dependencies.yaml; ASPS and assurance requirements live in assurance.yaml.

Treat those declarations as mandatory execution constraints. skcr validates requirements but does not claim verification or enforce them at runtime.

When to use

• modern JavaScript best practices decisions, controls, or operating practices need independent review.
• A change affects modern JavaScript best practices artifacts such as JavaScript source file or diff, async function and Promise chain, ES module or CommonJS module definition, closure and scope usage, prototype or class definition, runtime performance measurement.
• The user needs evidence-oriented findings for risks such as unhandled Promise rejection causing silent failure, async function called without await discarding returned Promise, mixing ES module import and CommonJS require causing resolution failure, closure over loop variable capturing reference instead of value, blocking main thread with synchronous computation delaying rendering or I/O, prototype mutation causing unexpected behaviour across module boundaries.
• Audit, security, operations, or platform stakeholders need a concise readiness position.
• Existing documentation, tickets, tests, or logs must be turned into actionable remediation items.

Operating model

1. Identify the relevant modern JavaScript best practices artifacts, owners, systems, environments, and review boundary.
2. Compare the available artifacts against expected signals such as ESLint no-floating-promises and no-async-promise-executor warnings, Node.js unhandledRejection event or browser console unhandled rejection, module bundler resolution warning, performance profile showing long task on main thread, memory leak detection from retained closure reference, code path analysis for unreachable Promise rejection handler.
3. Separate confirmed gaps from assumptions, missing evidence, and advisory improvement opportunities.