OpenParable
Skip to content
← Back to skills

Test Nodebridge Handler

Testing & Quality
test-nodebridge-handler

Test Nodebridge Handler is an Agent Skill for testing & quality published in the neovateai/neovate-code repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use this skill when testing NodeBridge handlers using `bun scripts/test-nodebridge.ts`, including listing available handlers and passing parameters

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/neovateai/neovate-code/blob/HEAD/.claude/skills/test-nodebridge-handler/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/test-nodebridge-handler, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Test NodeBridge Handler

Overview

This skill guides the process of testing NodeBridge message handlers using the test script.

Usage

List All Available Handlers

bun scripts/test-nodebridge.ts --list

Test a Specific Handler

bun scripts/test-nodebridge.ts <handler> [options]

Parameter Passing

Key-Value Format

bun scripts/test-nodebridge.ts handler.name --key=value --flag=true --count=42
  • Values are auto-converted: true/false → Boolean, numbers → Number
  • Boolean flags without value: --verbose becomes { verbose: true }

JSON Data Format

For complex data, use --data with JSON (takes priority over --key=value):

bun scripts/test-nodebridge.ts handler.name --data='{"key":"value","nested":{"foo":"bar"}}'

Available Handler Categories

CategoryExample Handlers
modelsmodels.list, models.test
configconfig.list
providersproviders.list
mcpmcp.list, mcp.getStatus
outputStylesoutputStyles.list
projectproject.getRepoInfo, project.workspaces.list
projectsprojects.list
sessionssessions.list
skillsskills.list, skills.get, skills.add, skills.remove, skills.preview, skills.install
slashCommandslashCommand.list
gitgit.status, git.detectGitHub
utilsutils.getPaths, utils.detectApps, utils.playSound

Examples

Test Model

bun scripts/test-nodebridge.ts models.test --model=anthropic/claude-sonnet-4-20250514
bun scripts/test-nodebridge.ts models.test --model=openai/gpt-4o --prompt="Say hello" --timeout=5000

List Models

bun scripts/test-nodebridge.ts models.list

Get File Paths

bun scripts/test-nodebridge.ts utils.getPaths --cwd=/path/to/dir --maxFiles=100

List Projects

bun scripts/test-nodebridge.ts projects.list --includeSessionDetails=true

Get Skill Details

bun scripts/test-nodebridge.ts skills.get --name=my-skill

Git Status

bun scripts/test-nodebridge.ts git.status --cwd=/path/to/repo

Output Format

The script outputs:

  1. Request - JSON of the data sent to the handler
  2. Response - JSON of the handler's return value with timing

Success response structure:

{
  "success": true,
  "data": { ... }
}

Error response structure:

{
  "success": false,
  "error": "Error message"
}

Notes

  • The script has a 30-second timeout for all requests
  • Exit code 0 on success, 1 on error
  • Use -h or --help for help message