Menu
Debug CLI and serial-to-HTTP bridge development for TeslaCANModder bench work and validation
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/babico/TeslaCANModder --skill tools-developmentThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Markdown linting for non-legacy TeslaCANModder docs. Triggers on any .md edit in docs/, *.md at root, or markdown-touching commits. Prevents CI markdown-lint failures (MD001 heading-increment etc.) by enforcing pre-commit lint, common gotchas, and config awareness.
Workflow for the TeslaCANModder legacy submodule sweep — fetch all 95+ submodules, identify those with new upstream commits, re-review the actual code (not just commit messages) for relevance to TeslaCANModder, skip the two repo-omitted upstreams, and handle 404/dead submodules by disabling them in-place. Codifies the project's preferred format and skip list.
Enforce asking the user for explicit permission before any git mutation in the TeslaCANModder repo (commit, push, merge, PR create, PR merge, release, force operations). Codifies the project's strict no-surprise git policy.
Based on SOC occupation classification
Showing SKILL.md
| name | tools-development |
| description | Debug CLI and serial-to-HTTP bridge development for TeslaCANModder bench work and validation |
| license | GPL-3.0 |
| compatibility | opencode |
| metadata | {"area":"tools","stack":"nodejs, typescript"} |
Guide agents through the TeslaCANModder debug CLI and tooling in tools/. I cover:
Use this skill when:
tools/scripts/tools/
├── commands/ CLI command implementations
├── lib/ shared utility modules
├── test/ Jest ESM tests
├── debug.js main CLI entry point
├── serial-http-bridge.js serial-to-HTTP bridge
├── package.json package manifest ("type": "module")
└── README.md tools documentation
scripts/
├── npm-audit-actionable.cjs security audit helper
├── release-matrix-smoke.mjs release smoke tests
└── validate-serial-contract.mjs serial contract validator
"type": "module" in package.json)camelCase for variables and functions.console.log.The debug CLI (tools/debug.js) provides bench work and validation commands:
node tools/debug.js <command> [options]
Common commands:
drive-context - capture and validate drive context signalsmonitor - live CAN frame monitoringflash - firmware flashing helperbridge - start serial-to-HTTP bridgeDrive context validation (for runtime signal releases):
node tools/debug.js drive-context --port COM5 --drive-duration 60000 --drive-min-samples 10 --drive-expect-full --drive-output artifacts/drive-context-report.json --drive-note-output artifacts/drive-context-note.txt
The bridge (tools/serial-http-bridge.js) proxies serial CAN frames to HTTP endpoints for integration testing.
Run tools tests:
npm run test:tools
Tests use Jest with native ESM support. Add tests for:
Workspace-level scripts in scripts/:
validate-serial-contract.mjs - Validates serial contract between firmware and protocol packagerelease-matrix-smoke.mjs - Smoke tests for release firmware matrixnpm-audit-actionable.cjs - Actionable security audit (run via npm run audit:ci)npm run test:tools and ensure all tests pass.npm run lint:all from repo root.tools/debug.js - CLI entry pointtools/serial-http-bridge.js - HTTP bridgetools/commands/ - CLI command implementationsscripts/validate-serial-contract.mjs - contract validatorscripts/release-matrix-smoke.mjs - release smoke tests