mix-compression

Installs rtk filters that compress verbose mix command output before it reaches the transcript.

537|38|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill mix-compression
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mix-compression
Source: https://github.com/oliver-kriska/claude-elixir-phoenix/tree/main/plugins/elixir-phoenix/skills/mix-compression
Command: npx skills add https://github.com/oliver-kriska/claude-elixir-phoenix --skill mix-compression

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rtk, and includes references (resource) components.

What problem does it solve?

Mix commands like mix test, mix credo, mix dialyzer, and mix compile emit verbose, repetitive output that floods the AI context window during long Elixir/Phoenix sessions, wasting tokens on progress noise while burying the signals that matter.

Core Features & Use Cases

  • Output compression via rtk: Installs six production-tested TOML filters that short-circuit happy paths to one line (e.g., "mix test: all pass") while preserving compile errors, test failures, dialyzer warnings, and stack traces verbatim.
  • Shell hook setup: Configures the rtk shell hook so mix X transparently becomes rtk mix X, filtering output at the subprocess layer before it enters the transcript.
  • Safe merging: Never overwrites an existing .rtk/filters.toml; diffs and merges only missing filters, then verifies everything with rtk verify.
  • Use Case: During a long /phx:investigate debugging loop that retries mix compile and mix test repeatedly, this skill cuts 5-15% of per-session tokens by collapsing passing runs while keeping every failure block intact.

Quick Start

Ask the AI to set up mix output compression with rtk filters so test, credo, and dialyzer output stops flooding the context.

Frequently Asked Questions about mix-compression

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

FAQPage Schema
How do I reduce mix test output noise in Claude Code sessions?

Install rtk and drop the bundled filters into .rtk/filters.toml. The mix-test filter short-circuits all-pass runs to a single line while preserving failure blocks, compile errors, and stack traces with file:line references.

What is rtk and how does it filter mix output?

rtk is a CLI proxy that intercepts terminal commands and filters their output through TOML regex rules before returning results. A shell hook rewrites mix X to rtk mix X transparently, so filtering happens at the subprocess layer before output reaches the transcript.

Does rtk filtering hide compile errors or test failures?

No. The filters are designed to never strip critical signals: CompileError blocks, test failure details, dialyzer warnings, and stack traces with file:line pass through unchanged. Only progress noise like Compiling N files and PLT checks is removed.

Will the rtk filters overwrite my existing .rtk/filters.toml?

No. If a project already has .rtk/filters.toml, the skill reads both files, presents a diff, and merges only the filters you do not already have. It never overwrites the existing file.

Why do my custom rtk filter regex patterns silently fail?

rtk uses Rust's regex crate, which does not support backreferences like \1 or \2. Any pattern using them will silently fail. Verify filters with rtk verify, which runs the embedded test fixtures for each filter.

How do I bypass rtk filtering for a single mix command?

Prefix the command with the shell builtin command, for example: command mix test. This bypasses the rtk shell hook and runs mix with raw, unfiltered output.