run-checks

Capture stdout and stderr from long-running CLI commands into log files.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/yearofthedan/weaver --skill run-checks-yearofthedan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-checks
Source: https://github.com/yearofthedan/weaver/tree/main/.claude/skills/run-checks
Command: npx skills add https://github.com/yearofthedan/weaver --skill run-checks-yearofthedan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Long-running build and test commands produce large mixed stdout/stderr streams and re-running them to see different sections wastes developer time and compute resources. This Skill teaches a simple pattern to capture the complete output on the first run so you can inspect any part later without re-executing expensive commands.

Core Features & Use Cases

  • Deterministic output capture: Use stream redirection with tee to persist combined stdout and stderr to a log file for later analysis.
  • Scoped test execution: Run targeted tests first to validate changes before running an entire suite, minimizing wasted runs.
  • Use Case: When a CI or local full-suite test run is slow, capture the first full run to a log and then diagnose failures or flaky tests by reading the saved output instead of re-running.

Quick Start

Capture the command output on the first run by piping combined stdout and stderr to tee and then read the generated log file to inspect failures or details without re-running the command.

Frequently Asked Questions about run-checks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture stdout and stderr from a long-running pnpm test command?

You can capture stdout and stderr by piping the combined output streams to tee, which persists the logs to a file for later analysis without re-running the command.

What is the best way to save CLI build output to a log file for later analysis?

The best way to save CLI build output is using stream redirection with tee to capture the complete stdout and stderr streams into a readable log file on the first run.

Why should I redirect command output to a log file instead of just re-running tests?

Redirecting command output to a log file saves compute resources and developer time by allowing you to inspect any section of the output later, avoiding the costly re-execution of slow test suites.

Can I run scoped pnpm tests first to avoid unnecessary full suite executions?

Yes, you can run targeted scoped tests first to validate changes, minimizing wasted runs and ensuring you only execute the full suite when necessary.

Does stream redirection with tee work for general build commands or only pnpm workflows?

Stream redirection with tee works for general build and test commands, as well as specific pnpm workflows like pnpm check and pnpm test, to capture durable output.

What are the limitations of using tee for capturing mixed stdout and stderr streams?

While tee captures combined stdout and stderr streams into a log file, you must read the generated log file manually to diagnose failures or flaky tests, as it does not parse the output automatically.