Agent skill

Rudu

by tanvesh01 in tanvesh01/rudu

Drive a live Rudu diff-review app session from the CLI. An agent skill from tanvesh01/rudu.

MITAuto-check passedDevelopment

Install Rudu

skills CLI
$ npx skills add tanvesh01/rudu --skill rudu -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tanvesh01/rudu rudu --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tanvesh01/rudu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/rudu .claude/skills/rudu && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rudu
GitHub stars
148
Token cost
~1.9k tokens
SKILL.md length
687 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Drive a live Rudu diff-review app session from the CLI. An agent skill from tanvesh01/rudu.

  • Works in 6 steps: Run review to understand the target. → Inspect existing GitHub threads, Comment… → Navigate to the relevant line. → …
  • Tasks that involve Pull requests
  • SKILL.md covers Open a session, Core workflow, Choose a local diff and Inspect, plus 5 more sections
  • Reaches github.com

What it does

Rudu is an agent skill from tanvesh01/rudu. Drive a live Rudu diff-review app session from the CLI. Open working-tree, commit, branch, patch, file, or pull-request diffs; inspect changes; steer the user's view; and manage local review notes and PR drafts.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. The repository describes itself as: Review PRs without losing your mind. The licence is MIT.

When your agent uses it

  • Tasks that involve Pull requests

Example prompts

  • “/rudu”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Run review to understand the target.
  2. Inspect existing GitHub threads, Comment Drafts, and local human notes before adding feedback.
  3. Navigate to the relevant line.
  4. Add a private note for analysis or conversation; create a Comment Draft only for intended GitHub feedback.
  5. Reply in the existing private note thread when answering the user.
  6. Never publish without an explicit user request. After publishing, report the returned review URL and any cleanupError.

What it can do on your machine

Read from SKILL.md and the folder at commit 3aa3988. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Rudu loads about 1.9k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tanvesh01/rudu at commit 3aa3988, republished under its MIT licence (© tanvesh01). 687 words, ~1,917 tokens.

Download SKILL.mdSave it as .claude/skills/rudu/SKILL.md (or your agent's skills folder).
name
rudu
description
Drive a live Rudu diff-review app session from the CLI. Open working-tree, commit, branch, patch, file, or pull-request diffs; inspect changes; steer the user's view; and manage local review notes and PR drafts.

Rudu

Rudu is a desktop diff-review app. The app window belongs to the user — never ask the user to click things for you. Use an open command to choose what Rudu displays, then rudu session * to inspect, navigate, and leave local notes.

Open a session

bash
rudu /path/to/repo                         # Working Tree Review
rudu diff main...HEAD                      # Selected Diff Review
rudu show HEAD                             # selected commit
rudu patch change.patch                    # patch file
rudu pr owner/repo#123                     # Pull Request Review
rudu pr https://github.com/owner/repo/pull/123
rudu skill path                            # print this skill's installed path

Open commands launch or focus the existing app. They return after Rudu accepts the request, not after the diff finishes rendering.

rudu session list returns persisted local checkouts, pull requests tracked in Rudu, and the current active target. With no selector, session commands use that active target. Use an explicit selector when needed:

text
--repo <path>                working tree for that checkout
--pr <url|owner/repo#number> that tracked pull request

Do not pass both. For a Selected Diff Review, omit --repo; passing it intentionally selects the checkout's Working Tree Review.

Core workflow

bash
rudu pr owner/repo#123
rudu session list
rudu session review
rudu session navigate --file src/app.ts --new-line 42
rudu session note add --author "Pi" --file src/app.ts --new-line 42 --body "Explain this edge case"
rudu session note list
rudu session note reply --author "Pi" --note NOTE_ID --body "Answer"
# Create a publishable draft only when GitHub feedback is intended:
rudu session comment draft --file src/app.ts --new-line 42 --body "Please handle this edge case"
# Only after the user explicitly asks to publish:
rudu session comment publish

All session output is JSON. Use --new-line for additions and --old-line for deletions; line numbers are 1-based.

Choose a local diff

Use Git's own revision syntax instead of inventing source flags:

bash
rudu diff                         # unstaged + untracked
rudu diff --staged                # staged
rudu diff HEAD                    # staged + unstaged + untracked
rudu show                         # latest commit
rudu show HEAD~1                  # selected commit
rudu diff main...HEAD             # merge-base/PR-style branch diff
rudu diff HEAD~3..HEAD -- src     # range limited by pathspec
rudu diff before.ts after.ts      # two files
rudu patch change.patch           # patch file
some-command-producing-patch | rudu patch -

These commands never mutate Git state. Review Notes on a Selected Diff Review are scoped to its exact source and resolved revision.

If a local review response contains relatedPullRequest, its current HEAD exactly matches a cached open PR. Keep reviewing the local target unless the user asks to switch; open the PR with rudu pr owner/repo#number when its GitHub context is needed. Absence means only that Rudu found no exact cached match.

Inspect

bash
rudu session review [--repo <path> | --pr <ref>] [--include-patch]

Local responses include:

text
kind, checkoutId, branch, headSha, revision, files, relatedPullRequest?

PR responses include:

text
kind, repo, number, headSha, summary, overview, checks, files

Overview or checks may have companion error fields while the diff remains usable. Add --include-patch only when raw unified diff is necessary; prefer local files when reviewing a checkout.

Navigate

bash
rudu session navigate [--repo <path> | --pr <ref>] \
  --file <path> (--new-line <n> | --old-line <n>)

Navigate before commenting so the user sees the code being discussed.

Private notes and PR comment drafts

bash
rudu session note add [--repo <path> | --pr <ref>] --author <name> --file <path> (--new-line <n> | --old-line <n>) --body <markdown>
rudu session note reply [--repo <path> | --pr <ref>] --author <name> --note <id> --body <markdown>
rudu session note delete [--repo <path> | --pr <ref>] --note <id> [--note <id> ...]
rudu session note delete [--repo <path> | --pr <ref>] --all
rudu session note list [--repo <path> | --pr <ref>] [--file <path>] [--type agent|user|all]
rudu session note promote [--repo <path> | --pr <ref>] --note <id>
rudu session comment draft [--repo <path> | --pr <ref>] --file <path> (--new-line <n> | --old-line <n>) --body <markdown>
rudu session comment delete [--repo <path> | --pr <ref>] --note <id> [--note <id> ...]
rudu session comment delete [--repo <path> | --pr <ref>] --all
rudu session comment list [--repo <path> | --pr <ref>] [--file <path>]
rudu session comment publish [--repo <path> | --pr <ref>]
  • Review Notes are private local annotations and are never published.
  • Agent notes and replies require --author; pass the agent's stable display name.
  • note promote copies a root private note into a publishable Comment Draft and preserves the note.
  • Comment Drafts are scoped to {repo, number, headSha} and require an exact PR target.
  • comment publish sends all root Comment Drafts as one comment-only GitHub review; local replies are not posted.
  • Publish only after the user explicitly asks. This action cannot be undone in Rudu.
  • A new PR head has a separate draft set.
  • comment list on a PR returns local commentDrafts and read-only githubThreads.
  • Reply only to IDs from private note list output; GitHub threads are read-only.
  • Deleting a root note also deletes its local replies.
  • note delete --all deletes private notes for the exact selected target; list first.
  • Publishing a Local Checkout requires its cached exact-head relatedPullRequest; invalid PR diff locations fail the whole publication and remain local.
  • Use note reply, not note add, when answering a human's local note.
  • --type user is the human-authored private-note channel; default is all private notes.
Show full SKILL.md (228 more words)Show less

Guiding a review

  1. Run review to understand the target.
  2. Inspect existing GitHub threads, Comment Drafts, and local human notes before adding feedback.
  3. Navigate to the relevant line.
  4. Add a private note for analysis or conversation; create a Comment Draft only for intended GitHub feedback.
  5. Reply in the existing private note thread when answering the user.
  6. Never publish without an explicit user request. After publishing, report the returned review URL and any cleanupError.

Important: only annotate lines in the diff

The diff view collapses unchanged regions. Notes on collapsed lines are invisible to the user — they count toward the file's comment badge but cannot be seen or interacted with.

Before adding a note or draft, use rudu session review --include-patch and check the @@ hunk headers to confirm the target line falls inside a rendered hunk. If the line you want to comment on is outside all hunks, either:

  • Pick the nearest changed line inside a hunk and reference the original line in your note body, or
  • Skip the note if no suitable anchor exists.

Common errors

  • "Rudu is not running" — open it with rudu <path> or rudu pr <ref>.
  • "no session matches repo" — run rudu <path> first.
  • "pull request ... is not tracked" — run rudu pr <ref> first.
  • "file not in the selected diff" — inspect session review and use one of its file paths.

© tanvesh01, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/rudu of tanvesh01/rudu.

Open the folder on GitHubat commit 3aa3988

Compare with similar skills

Rudu next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rudu compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rudu this skilltanvesh01/rudu148—~1.9kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
PR Design DocOpenHands/OpenHands90k—~2.4kAutomated safety check: PassMIT
WooCommerce Code Reviewwoocommerce/woocommerce11k3 repos~1.1kAutomated safety check: PassCustom licence

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed
  • WooCommerce Code Review

    woocommerce/woocommerce

    Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.

    11k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Record PR Demo

    payloadcms/payload

    A skill your agent uses when a Payload pull request needs a concise visual walkthrough for reviewers.

    45k GitHub stars~1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from tanvesh01/rudu

  • Clear this repo's local Rudu Tauri app state for first-run and onboarding verification.

    148 GitHub stars~457 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Rudu

What does Rudu do?

Drive a live Rudu diff-review app session from the CLI. An agent skill from tanvesh01/rudu. Rudu is an agent skill from tanvesh01/rudu. Drive a live Rudu diff-review app session from the CLI.

When should I use Rudu?

Rudu fits situations like: tasks that involve Pull requests.

How do I install Rudu in Claude Code?

Run `npx skills add tanvesh01/rudu --skill rudu -a claude-code`. Or copy the skill folder (skills/rudu in tanvesh01/rudu) into .claude/skills/rudu in your project. Claude Code loads it when a task matches its description.

How do I install Rudu in Codex?

Run `npx skills add tanvesh01/rudu --skill rudu -a codex`. Or copy the skill folder (skills/rudu in tanvesh01/rudu) into .agents/skills/rudu in your project. Codex loads it when a task matches its description.

Can I use Rudu in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tanvesh01/rudu --skill rudu -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rudu, .gemini/skills/rudu, .github/skills/rudu and .opencode/skills/rudu in your project.

What does Rudu need to run?

SKILL.md names no scripts, command-line tools or credentials: Rudu is instructions for the agent only.

Does Rudu access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Rudu safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rudu use?

Rudu is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rudu use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Rudu?

Skills that share tags, products or a category with Rudu: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rudu?

tanvesh01 (a GitHub user) maintains it in tanvesh01/rudu, which has 148 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 10, 2026.

Source: tanvesh01/rudu on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.