Open CLI

traces

scriptableproductivity
$ npm i -g @traces-sh/traces
Summary

Terminal traces, workflow recording, and debugging sessions from the terminal.

  • traces fits git & github well, especially for terminal traces, workflow recording, and debugging sessions from the terminal.
  • 248 npm weekly downloads.
  • Easy to automate.
  • Good fit for coding-agent workflows and repeatable scripts.
  • Output is mostly text-first, so verify results before scripting around it.
github-traces-SKILL.md

Traces guide

Terminal traces, workflow recording, and debugging sessions from the terminal. Built by Traces.

Open CLI packages the install path, verify step, and safe-start workflow so this tool can move from “interesting CLI” to something you can actually use. It also integrates with skills.sh so each CLI comes with the right companion skills, not just a binary and a docs link.

When to apply

  • terminal traces, workflow recording, and debugging sessions from the terminal.
  • You need productivity workflows in both local dev and CI.
  • You need terminal traces.
  • You need workflow recording.
  • You need debugging sessions.

Quick reference

Installnpm i -g @traces-sh/traces
Verifytraces --version
First real commandtraces record npm run dev

Open CLI × skills.sh

Open CLI integrates traces with the right skills.sh companions so you get the tool and the workflow together.

Monitoring & Observability

Verified pairing

Open CLI integrates traces with this skills.sh skill because it is the clearest fit for how traces is usually used. Use metrics, traces, and health checks to understand what your CLI changed.

View on skills.sh
$ npx skills add https://github.com/supercent-io/skills-template --skill monitoring-observability
Starter prompt

Use traces together with the Monitoring & Observability skills.sh skill. Start with safe inspection commands, summarize what you find, and ask before any step with side effects.

Also useful from skills.sh
Log Analysisskills.shDebuggingskills.sh

Why this tool

  • traces fits git & github well, especially for terminal traces, workflow recording, and debugging sessions from the terminal.
  • 248 npm weekly downloads.
  • Easy to automate.

Watch-outs

  • Output is mostly plain text.

Example workflow

1. traces record npm run dev

Safe start

Step 1

Install traces.

Step 2

Run `traces --version` first.

Step 3

Start with `traces record npm run dev`.

Step 4

Install the CLI and make sure it is on your PATH.

Alternatives worth considering

prettier

Formatting, markdown, and code consistency from the terminal.

eslint

Linting, js rules, and code health from the terminal.

vitest

Testing, watch mode, and js unit tests from the terminal.