rtk-ai/rtk

feat(hook): add fd rewrite rule to compact output

Open

#1,668 opened on May 1, 2026

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

Repository metrics

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

Description

Problem

fd is commonly used as a find replacement in Claude Code sessions (via CLAUDE.md rules). RTK rewrites find to rtk find (compact tree output), but fd passes through unmodified.

Real-world example:

  • fd '\.py$' /path -> 433 lines raw output
  • rtk find /path -name '*.py' -> 17 lines (compact tree)

That's a 96% reduction that fd users miss entirely.

Proposed solution

Option A: Add rtk fd subcommand that wraps fd and compacts the output (same tree format as rtk find).

Option B: Add a hook rewrite rule mapping fd -> rtk find with argument translation (fd 'pattern' -> rtk find . -name 'pattern').

Option A is cleaner since fd and find have different argument syntax.

Context

rtk hook check "fd '*.py'" returns "No rewrite" today. The [hooks] config section only has exclude_commands, no custom rewrite mappings.

Contributor guide

Research direction
Study the existing hook rewrite mechanism in the codebase, particularly how the `find` command is rewritten to `rtk find`. Then implement a similar rewrite rule for the `fd` command, translating its arguments to match `rtk find` syntax.
Tech stack
rust
Domain
cli
Issue type
Feature
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
Rust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75