Conversation
* fix: curl size guard (#297) + exclude_commands config (#243) **#297 — curl JSON inflation guard** - `rtk curl` no longer replaces small JSON responses with a type schema that is larger than the original payload - Size guard in `filter_curl_output()`: only return schema when `schema.len() <= original.len()` - Inspired by PR #324 (@rursache) **#243 — exclude_commands config** - Add `[hooks] exclude_commands = ["curl"]` in config.toml to prevent the auto-rewrite hook from rewriting specific commands - Survives `rtk init -g` re-runs (config.toml is user-owned) - Implemented in `rewrite_cmd::run()` via `HooksConfig` struct - Threaded through `rewrite_command()` → `rewrite_compound()` → `rewrite_segment()` Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: add #297 and #243 to CHANGELOG + exclude_commands in README * docs: fix version references 0.24.0 → 0.25.0 across all docs --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* feat: add Claude Code skills for PR and issue triage Two skills that power structured audits directly in Claude Code sessions. They replace ad-hoc manual reviews with a repeatable, documented workflow. **`/pr-triage`** — Pull request audit Scans open PRs, runs deep review on selected ones, and posts formatted review comments to GitHub. Covers code quality, test coverage, security surface, and alignment with CLAUDE.md conventions. Useful before every merge and for contributor onboarding. **`/issue-triage`** — Issue audit Audits open issues, auto-categorizes (bug/feature/doc/question), detects duplicates, cross-references related PRs, and estimates risk/priority. Posts structured comments so maintainers have a clear action queue. Both skills integrate with the `gh` CLI and can be invoked with args: /pr-triage 42 57 — deep review of specific PRs /pr-triage all — full audit of all open PRs /issue-triage — audit-only mode (no comments posted) /issue-triage all en — deep analysis, English output These reduce the overhead of code review and issue management to a single slash command, keeping context inside the Claude Code session. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: fix version references 0.24.0 → 0.25.0 and module count (pre-existing) --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…347) - #345: rewrite_segment() now returns None when env_prefix contains RTK_DISABLED= — prevents rewriting commands the user explicitly opted out of - #346: rewrite_compound() detects redirect operators (2>&1, >&2, &>/dev/null, &>>) before treating bare & as background operator — fixes corrupted compound commands containing stderr redirects - #347: validate_json_extension() helper added to json_cmd.rs — early rejection with clear error message for TOML/YAML/XML/CSV/etc. files, with a dedicated tip for Cargo.toml (suggests rtk deps) Tests: 16 new unit tests (4 + 6 + 6), 7 new hook integration tests. All 672 tests pass. Quality gate clean. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Version mentions (README.md, CLAUDE.md, ARCHITECTURE.md) were still on 0.25.0. Module count was 56 (missed hook_check module added in #350). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
gh commands with --json, --jq, or --template produce structured output that rtk gh filtering would corrupt. Skip rewrite so callers get raw JSON.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
) Two fixes for command passthrough issues: 1. Restore `--` separator stripped by clap (#287): When running `rtk cargo test -- --nocapture`, clap consumes `--` and passes only `["--nocapture"]` to cargo, which rejects it. Now detect `--` from the original command line and re-insert it in the correct position. 2. Remove noisy `[rtk: parse failed, running raw]` stderr message (#286): Unrecognized commands like `rtk make` or `rtk ruby` pass through silently via the fallback, matching the documented behavior. Fixes #286 Fixes #287
…ommands (#336) (#363) The rewrite pattern matched all `docker` commands but the regex didn't cover `docker compose`, so compose subcommands were never rewritten. Meanwhile unsupported compose commands (up, down, config) would fail if manually prefixed with rtk. - Extend regex to match `docker compose (ps|logs|build)` - Unsupported compose subcommands (up, down, config, exec, etc.) are correctly skipped by the regex and not rewritten - 6 new tests covering supported and unsupported compose subcommands Fixes #336
* fix: prettier reports "All OK" when not installed (#221) Empty or failed prettier output was incorrectly treated as "all files formatted". Now detects empty output and non-zero exit code, shows the actual error message instead of a false positive. * test: add smoke tests for rewrite, verify, proxy, discover, diff, wc, smart, docker, json edge cases Covers bug fixes #196, #344, #345, #346, #347 and previously untested commands. Adds assert_fails helper. 118 assertions total (was 69). * chore: update benchmark.sh with missing commands and fix paths - Add cargo (build/test/clippy/check), diff, smart, wc, curl, wget sections - Fix Python commands: use dedicated rtk ruff/pytest instead of rtk test - Fix Go commands: use dedicated rtk go/golangci-lint, add go build/vet - Make BENCH_DIR absolute so debug files work from temp fixture dirs - Fallback to installed rtk if target/release/rtk not found
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix: gh pr edit/comment pass correct subcommand to gh
pr_action was receiving the past-tense display label ("edited",
"commented") and using it as both the gh subcommand and the
ok_confirmation message. This caused `gh pr edited` to be invoked
instead of `gh pr edit`, which fails with "unknown flag" errors.
Split the parameter into subcmd (for the gh invocation) and
display_label (for ok_confirmation output).
* smaller diff
gh view/checks commands (pr view, issue view, pr checks, run view) were ignoring extra flags like -R/--repo, causing failures outside git repositories where gh needs -R to know which repo to query. The root cause: these functions took args[0] as the identifier and discarded everything else, while constructing hardcoded gh commands. Changes: - Add extract_identifier_and_extra_args() to separate the positional identifier from flags, handling both `view 123 -R owner/repo` and `view -R owner/repo 123` argument orders - Pass extra args through to gh in view_pr, view_issue, pr_checks, and view_run - Add has_json_flag() check at top of run() to passthrough when user explicitly requests --json output (related fix from #313) Fixes #223
When running `rtk lint npx eslint ...`, args[0] was "npx" instead of "eslint", causing no JSON format flag injection and duplicated output. Extract strip_pm_prefix() and detect_linter() helpers, skip package manager prefixes before identifying the actual linter name.
* docs: revamp README with logo, badges, and cleaner structure - Add centered logo (og-image) and tagline - Add badges: CI, release version, license, Discord, Homebrew - Add language links placeholder (fr, zh, ja, ko, es) - Fix Linux binary filename (gnu -> musl) — fixes #323 - Put Homebrew as recommended install method - Simplify and reorganize all sections (871 -> ~360 lines) - Add Discord invite link - Remove verbose troubleshooting (link to TROUBLESHOOTING.md instead) - Remove detailed security review section (link to SECURITY.md) * docs: add translated READMEs (fr, zh, ja, ko, es) Add localized README files linked from the main README language selector: - README_fr.md (French) - README_zh.md (Chinese) - README_ja.md (Japanese) - README_ko.md (Korean) - README_es.md (Spanish) Each translation includes: installation, quick start, commands overview, how it works diagram, and links to documentation. * docs: use rtk-ai org avatar as logo in all READMEs
* fix: reduce gh diff / git diff / gh api truncation (#354) - compact_diff: increase max_hunk_lines 10→30, max_lines default 100→500 - gh api: passthrough instead of JSON→schema destruction - gh pr diff: add --no-compact flag + increase limit to 500 - gh pr view: passthrough when --json/--jq/--web provided by user Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * docs: update version reference 0.26.0→0.27.1 in README * docs: update version reference 0.26.0→0.27.1 in CLAUDE.md * docs: update version reference 0.26.0→0.27.1 in ARCHITECTURE.md * fix: resolve compile errors in gh_cmd.rs (type mismatches) * fix: use explicit .iter() in pr_diff loop (avoids &&[String] ambiguity) * docs: fix version reference 0.27.x→0.27.1 in README * fix: remove shadowed extra_args in view_pr (was &&[String] not iterator) --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sends an embed with version, release notes, and link to the GitHub release page via the RTK_DISCORD_RELEASE webhook secret.
docs: add contributing.md guide
Update README.md
- Create docs/FEATURES.md with all 45+ commands documented (syntax, options, examples, token savings) - Create docs/GUIDE.md with getting started, workflows per language, Claude Code integration, FAQ, troubleshooting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.