rtk-ai/rtk

Add rtk cmake filter (collapse build progress, keep diagnostics)

Open

#2,236 opened on Jun 3, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (2,914 forks)batch import
area:clienhancementhelp wantedpriority:medium

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 8d 17h) (49 merged PRs in 30d)

Description

Summary

Add an rtk cmake filter. cmake --build (and configure) output is verbose and dominated by progress/percentage lines that carry little signal once a build succeeds, but is a high-frequency command in C++ workflows.

Why

rtk discover flagged cmake as the #1 unhandled command in my history: 147 invocations over 30 days (e.g. cmake --build cmake-build-debug --target ...), with no RTK equivalent. C++ build/test loops run this constantly.

What's noisy

  • [ NN%] Building CXX object ... progress lines (one per TU)
  • Scanning dependencies of target ...
  • Repeated make[1]/make[2] directory-entry chatter

Suggested behavior

  • On success: collapse per-TU progress to a count (e.g. "Built N targets, M objects"), keep warnings/errors verbatim.
  • On failure: preserve the failing compiler invocation + diagnostics in full; drop unrelated progress.
  • Keep cmake configure output's cache/feature summary but drop the line-by-line check spam.

Contributor guide

Research direction
Study existing rtk filters (e.g., cargo) to understand the filter interface. Implement a new filter for cmake that collapses progress lines while preserving warnings and errors. Test with various cmake outputs.
Tech stack
rust
Domain
clideveloper experiencebuild system
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustCLI basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60