rtk-ai/rtk

Inconsistent scope defaults: rtk discover (project) vs rtk gain (global)

Open

#1,582 opened on Apr 28, 2026

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

Repository metrics

Stars
 (48,085 stars)
PR merge metrics
 (Avg merge 11d 1h) (45 merged PRs in 30d)

Description

Problem

rtk discover and rtk gain have inconsistent scope defaults AND the --all flag means different things on each:

Command Default scope --all means
rtk discover current project scan all projects
rtk gain global (all projects) show all time breakdowns (daily + weekly + monthly)

So --all means "widen scope" on discover but "widen time range" on gain. Running both commands to understand RTK coverage requires opposite flags for scope, and --all is a footgun that does something unexpected on gain.

Expected

  1. Consistent scope defaults — both should default to global (more useful), with --project to narrow
  2. Consistent --all semantics — or avoid reusing --all for unrelated purposes across commands

Suggested fix

  • rtk discover: default to global, add --project flag to narrow (matching rtk gain)
  • Rename rtk gain --all to something like --full or --breakdown to avoid the semantic collision

Contributor guide

Research direction
Review the CLI argument definitions for 'rtk discover' and 'rtk gain' commands. Locate the default scope setting and change 'discover' default to global. Then find the ' all' flag in 'gain' and rename it to ' full' or similar, updating documentation and tests accordingly.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75