Why is it important to separate stdout and stderr in hooks?

Mixing stderr (logs/errors) and stdout (data) can corrupt the JSON output expected by the hook caller, causing parsing failures in the automation pipeline.

How does this framework handle script timeouts?

It utilizes the shell 'timeout' command to wrap Node execution, allowing the hook to identify hang-ups and provide a graceful fallback or advisory warning.

Does this replace hook governance frameworks?

No, this skill focuses on the execution reliability of individual scripts, while governance frameworks handle the overarching policy and execution order of multiple hooks.

Is this skill specific to Salesforce?

While developed for Salesforce RevOps workflows within the OpsPal ecosystem, the hardening patterns apply to any shell environment invoking Node.js scripts.

What is an exit code contract?

It is a predefined map of Node.js exit codes (like 0 for success, 124 for timeout) that dictates how the parent shell script should interpret and react to the script's outcome.

Hook Node Execution Hardening

Name: Hook Node Execution Hardening
Author: RevPalSFDC

byRevPalSFDC

•

開発者ツール

Hardens inline Node.js execution in shell hooks by implementing deterministic I/O contracts and robust failure propagation.

This skill provides a standardized framework for hardening Node.js scripts called within shell hooks, ensuring they operate reliably in complex development environments like Salesforce RevOps. It addresses common failure points such as process crashes, execution timeouts, and JSON output corruption by enforcing strict separation of stdout and stderr. By implementing these patterns, developers can ensure that hook logic remains deterministic, errors are captured without breaking the data stream, and scripts adhere to strict execution budgets to prevent hanging processes.

主な機能

01Provides advisory fallback patterns for non-critical validation errors

02Separates Node.js stdout from stderr to prevent JSON response corruption

03Defines a standardized exit code contract for consistent failure handling

04Enforces strict execution timeout budgets using the timeout command

051 GitHub stars

06Includes guidance for Node binary discovery in diverse runtime contexts

ユースケース

01Capturing detailed Node.js error diagnostics without interfering with automated hook results

02Implementing timeout-protected metadata checks in Salesforce development workflows

03Running custom Node.js validation logic within Git pre-commit or pre-push hooks

主な機能

01Provides advisory fallback patterns for non-critical validation errors

02Separates Node.js stdout from stderr to prevent JSON response corruption

03Defines a standardized exit code contract for consistent failure handling

04Enforces strict execution timeout budgets using the timeout command

051 GitHub stars

06Includes guidance for Node binary discovery in diverse runtime contexts

ユースケース

01Capturing detailed Node.js error diagnostics without interfering with automated hook results

02Implementing timeout-protected metadata checks in Salesforce development workflows

03Running custom Node.js validation logic within Git pre-commit or pre-push hooks