REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
a code review TUI with vim keybindings
제작자라면 이 코드를 README에 붙여 넣으세요. 배지는 이 페이지로 연결됩니다.
[](https://mcp.popnx.com/en/skills/agavra-tuicr)같은 작업에서 AI를 서비스에 연결하는 MCP
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
MCP server for terminal commands, file operations, and process management
같은 종류의 작업, Skill 목록과 같은 순서
| 이 항목 tuicr | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| 제작자 | agavra | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skill 수 | 1 | 1 | 1 | 1 | 1 |
| GitHub 별 | 3,616 | 467,235 | 234,125 | 149,873 | 144,332 |
| 마지막 코드 변경 | 2026년 11월 17일 | 2026년 11월 18일 | 2026년 4월 20일 | 2026년 11월 18일 | 2026년 11월 18일 |
| 라이선스 | MIT | MIT | – | Apache-2.0 | MIT |
agavra의 Skill(지시 묶음) 1개, AI가 읽고 그대로 일해요 · MCP server가 아니에요
MCP = 손
AI를 외부 서비스나 데이터에 연결합니다(예: Notion 읽기, 청구서 만들기). 프로그램이나 서버가 실행 중이어야 합니다.
Skill = 안내서
작업 방법을 AI에게 가르치는 텍스트 파일. 어떤 서비스에도 연결되지 않습니다.
겹치는 경우도 있습니다. 도구를 부르는 스크립트가 있는 Skill도, 지식만 보내는 MCP도 있습니다. 하려는 작업을 기준으로 고르세요.
CodexCursor
제작자 README와 repo 폴더 기준
GitHub account agavra (person), 13 years old
★ 3,616 stars · code last changed 2026년 11월 17일
6 scripts that can run on a computer: tuicr-wrapper-cmux.sh, tuicr-wrapper-herdr.sh, tuicr-wrapper-rex.sh, tuicr-wrapper-zellij.sh and 2 more
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 62d172d (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
먼저: 어떤 AI를 쓰시나요
쓰는 앱을 고르면 그 앱의 설치 방법만 보여 드립니다
Files are byte-for-byte the same as on GitHub at commit 62d172d · View on GitHub ↗
6 scripts
Once uploaded it runs on Claude’s systems, not on your computer. No need to unzip
All 8 files · 47 KB
SKILL.md14 KB_tuicr-common.sh3 KBtuicr-wrapper-cmux.sh5 KBtuicr-wrapper-herdr.sh6 KBtuicr-wrapper-rex.sh5 KBtuicr-wrapper-zellij.sh8 KBtuicr-wrapper.sh6 KBLICENSE1 KB+Create skillUpload a skillpick tuicr.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026년 11월 12일 · Source: support.claude.com, support.claude.com, code.claude.com
이 문장을 복사해 Claude Code 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Claude Code를 다시 열고 /tuicr를 입력하거나 관련 작업을 요청하면 Claude가 알아서 써요
Checked against official docs 2026년 11월 12일 · Source: code.claude.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
git clone --depth 1 https://github.com/agavra/tuicr.git /tmp/popnx-skill-agavra-tuicr-62d172d && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-agavra-tuicr-62d172d/skills/tuicr' ~/.claude/skills/tuicrChatGPT 데스크톱 앱에는 Codex가 들어 있고, Codex는 ~/.agents/skills 폴더에서 Skill을 읽습니다
ChatGPT 데스크톱 앱에서 Codex를 열고 이 문장을 채팅에 붙여 넣으세요
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
tuicr 폴더를 ~/.agents/skills/tuicr에 넣으세요
~는 홈 폴더($HOME)입니다
터미널 없이: ZIP을 내려받아 압축을 풀고 tuicr 폴더를 ~/.agents/skills로 옮기세요
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
git clone --depth 1 https://github.com/agavra/tuicr.git /tmp/popnx-skill-agavra-tuicr-62d172d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-agavra-tuicr-62d172d/skills/tuicr' ~/.agents/skills/tuicrChecked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
직접 설치한 Skill은 쓸 수 없고, 디렉터리의 플러그인에 들어 있는 Skill만 쓸 수 있습니다
이 Skill을 ChatGPT에서 쓰려면 위 방법대로 ChatGPT 데스크톱 앱을 쓰세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
이 문장을 복사해 Codex 채팅에 붙여 넣으세요 · ChatGPT 데스크톱 앱 안의 Codex, Codex CLI, IDE 확장 프로그램에서 모두 쓸 수 있습니다
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex는 새로 설치한 Skill을 스스로 찾습니다. 보이지 않으면 Codex를 다시 시작하세요 · 쓰는 법: ChatGPT에서는 @를 입력하고 Skill을 고르세요 · Codex CLI나 IDE 확장 프로그램에서는 /skills를 실행하거나 $ 뒤에 Skill 이름을 입력하세요
Checked against official docs 2026년 11월 15일 · Source: learn.chatgpt.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
git clone --depth 1 https://github.com/agavra/tuicr.git /tmp/popnx-skill-agavra-tuicr-62d172d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-agavra-tuicr-62d172d/skills/tuicr' ~/.agents/skills/tuicr이 문장을 복사해 Cursor 채팅에 붙여 넣으세요
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Cursor Agent 채팅에서 /를 입력하고 tuicr 선택
Checked against official docs 2026년 11월 12일 · Source: cursor.com
Skill은 AI가 따르는 지시예요. 설치 전에 파일을 읽고, 믿을 수 있는 제작자 것만 설치하세요.
Mac: Command+스페이스 후 Terminal 입력 · Windows: 아래 명령은 PowerShell에서 안 돼요. 위의 “AI에게 설치 맡기기”를 쓰세요
repo를 임시 폴더에 내려받고 SKILL.md가 있는 폴더만 복사해요
git clone --depth 1 https://github.com/agavra/tuicr.git /tmp/popnx-skill-agavra-tuicr-62d172d && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-agavra-tuicr-62d172d/skills/tuicr' ~/.cursor/skills/tuicrSkill을 읽을 수 있는 다른 앱용입니다. 이 문장에는 Claude Code, Codex, Cursor 경로가 들어 있어 AI가 쓰는 앱에 맞게 고릅니다 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026년 11월 12일 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Gemini CLI, GitHub Copilot 같은 다른 Agent Skills 지원 앱은 폴더가 달라요. 그 앱 안내를 보고 SKILL.md가 있는 폴더를 복사하세요.
2026년 11월 11일에 Claude Code, Codex, Cursor 공식 안내로 skill 폴더 확인
✓ 명령 확인 2026년 11월 18일
아래 글은 제작자 repo에서 온 것이며 PopNx MCP의 지시가 아니에요
처음 8,000자 표시 · GitHub에서 전체 파일 열기
---
name: tuicr
description: Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, Rex, tmux, Zellij, or Herdr when a user needs an interactive review pane.
---
# 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:
```bash
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.
3. Choose the session:
- If the CLI clearly reports exactly one relevant active session with
`"active": true`, attach to it.
- If multiple sessions are active, or the correct session is not clear, ask
the user which slug to use. One repo can hold a worktree and a
commit-range session at once, and adding to the wrong one exits 0.
- If the user provided a slug or session JSON path, use it directly.
- For a PR review, pass the PR slug from the listing (e.g.
`gh:owner/repo/pr/N`) to `--session`; it is self-contained and needs no
`--repo`.
- If there is no active session, start or wait for one as described below.
- Until active-session discovery is formalized as a stable protocol, treat
`"active": true` as a convenience signal. If slug resolution fails, ask the
user for the slug or repo path used by the session.
The CLI works even if the agent is not running inside tmux, Zellij, or Herdr,
so do not require a multiplexer just to connect to an existing active session.
## Start A Session
When the user needs an interactive tuicr pane and no active session exists:
| Environment | Action |
|-------------|--------|
| `$CMUX_WORKSPACE_ID` is set | Run `tuicr-wrapper-cmux.sh /path/to/repo -- <scope>` |
| `$REX_SESSION` is set | Run `tuicr-wrapper-rex.sh /path/to/repo -- <scope>` |
| `$TMUX` is set | Run `tuicr-wrapper.sh /path/to/repo -- <scope>` |
| `$ZELLIJ` is set | Run `tuicr-wrapper-zellij.sh /path/to/repo -- <scope>` |
| `$HERDR_ENV` is `1` | Run `tuicr-wrapper-herdr.sh /path/to/repo -- <scope>` |
| None is set | Tell the user you are waiting for them to start `tuicr` in the repo, then attach with `tuicr review list` after they say it is ready |
`<scope>` is `-w` for uncommitted working-tree changes or `-r <revset>` for a
commit range — always pass one explicitly so the user is never left to pick
staged/unstaged/commit-range manually in the TUI.
If more than one multiplexer marker is set, prefer the innermost multiplexer if
that is clear; otherwise ask. cmux hosts a Ghostty terminal, so `$TERM_PROGRAM`
reads `ghostty` inside cmux — check `$CMUX_WORKSPACE_ID`, not the terminal name.
tuicr supports both git and Jujutsu (jj) repositories, and jj workspaces may
have no `.git` directory at all. Do not pre-check the directory with
`git rev-parse` or refuse to launch because git does not recognize it; always
run the wrapper and let it validate the repository.
Wrapper paths are relative to this skill directory:
```bash
<skill-directory>/tuicr-wrapper-cmux.sh /path/to/repo -- -w
<skill-directory>/tuicr-wrapper-rex.sh /path/to/repo -- -w
<skill-directory>/tuicr-wrapper.sh /path/to/repo -- -w
<skill-directory>/tuicr-wrapper-zellij.sh /path/to/repo -- -w
<skill-directory>/tuicr-wrapper-herdr.sh /path/to/repo -- -w
```
The Herdr wrapper requires `jq` to read pane IDs and completion results from
Herdr's JSON responses. The Rex wrapper requires `jq` to read the new block ref
from `rex split --json`.
Every wrapper accepts pass-through tuicr arguments after `--`, which is how
you scope the review instead of leaving the scope selector for the user to
fill in — for example `-- -w` for uncommitted working-tree changes or
`-- -r <revset>` for a commit range. Always pass one of these explicitly when
launching a review pane.
If your tool supports command timeouts, use a long timeout, such as 10 minutes,
because the tmux, Zellij, and Herdr wrappers wait for the TUI to exit. The cmux
and Rex wrappers are the exception: they return as soon as the pane is running.
When another tuicr is already open where the new pane would go (the caller's
tmux window; the same repository under Zellij), the tmux and Zellij wrappers
wait for it to close before opening a new pane, for up to `TUICR_WAIT_TIMEOUT` seconds (default 300). If it is still open
after that, they exit 75 without opening anything: rerun the command, and don't
treat it as an empty review. A tuicr in another tmux window, such as another
agent session's, doesn't make the tmux wrapper wait.
The cmux wrapper prints the new surface ref between `=== TUICR SURFACE ===`
markers; capture it to close the pane later with
`cmux close-surface --surface <ref>`. The Rex wrapper prints the new block ref
between `=== TUICR BLOCK ===` markers; capture it to close the block later with
`rex block close <ref>`.
Once the TUI creates its active session, use
`tuicr review list --repo /path/to/repo` to capture the slug. If your
environment cannot run another command while a blocking wrapper is waiting,
read the comments after the user exits tuicr.
## Reconstruct The Diff
To review a patch yourself, rebuild the diff the user sees. The slug's source
segment says which:
| Slug segment | Diff |
|--------------|------|
| `worktree/<head>`, `staged-and-unstaged/<head>` | `git diff HEAD` |
| `staged/<head>` | `git diff --cached` |
| `unstaged/<head>` | `git diff` |
| `commits/<base>..<head>` | `git diff <base>~1..<head>` |
| `pr/<n>` | `gh pr diff <n>` |
| `pristine` | none; every tracked file shown in full |
Range endpoints are inclusive and printed oldest-first, so `<base>` without
`~1` drops the first commit. Check the file count against the listing row's
`file_count`; a mismatch means every line number you derive will be wrong.
## Read User Comments
This is the main review loop for user-led review.
There is no push stream from tuicr to the agent. Read comments by running the
CLI on demand. After the user says comments are ready, or after the TUI exits,
run:
```bash
tuicr review comments --repo질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.