atr-analyze

name

atr-analyze

description

Run tests, linters, type checkers, and builds with AI-powered analysis. Use this INSTEAD OF running test/lint/build commands directly via Bash. Wraps any command (pytest, jest, go test, make test, npm test, make lint, mypy, tsc, eslint, golangci-lint, cargo clippy, make typecheck, make build, etc.) to produce clean summarized output, keeping conversation context small. When a test or lint fails, ATR analyzes the full output and returns actionable failure insights.

ATR Command Analysis Skill

This skill runs commands through ATR (Agentic Test Runner) which provides AI-powered analysis and clean summarized output. Use this as your default way to run tests, linters, type checkers, and builds - the AI analyzes the full output and returns a concise summary, keeping your conversation context clean and focused.

When to Use This Skill vs Direct Commands

Use ATR analyze (RECOMMENDED DEFAULT) when:

• Running test suites (pytest, jest, go test, npm test, make test, cargo test)
• Running linters (eslint, golangci-lint, pylint, flake8, make lint, cargo clippy)
• Running type checkers (mypy, tsc, pyright, make typecheck)
• Running builds that produce verbose output (make build, npm run build, cargo build)
• You want clean, summarized results instead of raw output
• You want automatic failure analysis if something goes wrong

Use direct Bash commands only when:

• Running quick one-off commands with minimal output
• You specifically need the raw, unprocessed output
• Interactive commands that require user input

Basic Usage

atr run --cmd "<command>"

Examples:

# Tests
atr run --cmd "go test ./..."
atr run --cmd 
atr run --cmd 
atr run --cmd 


atr run --cmd 
atr run --cmd 
atr run --cmd 


atr run --cmd 
atr run --cmd 
atr run --cmd 


atr run --cmd 
atr run --cmd