Към всички skills

tuicr

agavra · Инструменти

Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.

Оригинален текст · няма потвърден превод на български

Теми: ai-tools · code-review · rust · tui

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
3174
Лиценз
MIT
Последна проверка на записа
22.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add agavra/tuicr

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

tuicr Review Workflow

Use tuicr review as the default agent interface. The TUI is where the human reviews code; the CLI is how the agent discovers active sessions, reads user comments, and, only when appropriate, adds agent-authored comments.

Core Rule

First decide which workflow the user is asking for:

  1. User-led review of agent-generated changes

    • The user wants to inspect the patch and write comments in tuicr.
    • Your job is to open or find the session, then retrieve the user's comments with tuicr review comments when they say comments are ready. If you are explicitly waiting while the user reviews, poll the same command periodically and look for new comment IDs.
    • Do not add your own review comments, do not preemptively review your own patch, and do not impersonate the user's comments.
  2. Agent review of an AI-generated patch

    • The user wants you to understand, critique, or summarize a patch.
    • You may inspect the patch and propose findings.
    • If you can confidently identify this workflow and the target session, add findings directly with tuicr review add and an explicit --username identifying the agent. Ask first when the workflow or session is ambiguous.

If the user's intent is ambiguous, ask which workflow they want.

Attach To A Session

  1. Determine the repository directory from the user's request, current working directory, or recent file operations. Ask if it is ambiguous.

  2. List persisted sessions:

    tuicr review list --repo /path/to/repo   # checkout + its repo's PR sessions
    tuicr review list --repo owner/repo      # all sessions for a forge repo
    tuicr review list --all                  # every session across all repos
    

    --repo is a selector: a checkout path also surfaces PR sessions for that checkout's origin repo, and a forge coordinate like owner/repo matches local and PR sessions by owner/repo. Each row carries a kind (local or pr) and a usable slug. Use --all when you don't know the repo.

    [] with exit 0 also means "not a repo root" — a subdirectory returns it too. Pass the root, then --all, before concluding nothing is open.

Целият SKILL.md в GitHub