القائمة
Use when an agent needs to run the local roder TUI in tmux, send text or keys into the session, inspect panes, and capture pane output as timestamped .txt and .png artifacts.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Draft release notes for Roder releases, new crates or packages, feature additions, behavior changes, and fixes. Use when writing release notes, changelog summaries, release announcements, or explaining what changed in a branch, PR, crate, SDK, or package release.
Use when editing TUI rendering code, adding new visible surfaces, or working on themes/CSS in Roder. Keeps class/id taxonomy, cascade order, and the supported CSS subset consistent across sessions.
Draft a changelog entry from the latest changes.
Use when a user asks for an orientation tour of an unfamiliar repository. Produces a structured tour of entry points, key modules, and how to run tests.
Use when a PR changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, when adding a new crate or package to the release config, or when working on knope versioning/release automation. For the step-by-step workflow to add a change file, use $create-changeset.
Use when a PR or branch changes any released package (crates/*, sdk/typescript, sdk/python, packages/edit-tools), when the changeset-gate CI check fails, or before pushing work that touches versioned package directories. Creates the required .changeset/*.md file for knope per-package versioning.
| name | roder-tmux |
| description | Use when an agent needs to run the local roder TUI in tmux, send text or keys into the session, inspect panes, and capture pane output as timestamped .txt and .png artifacts. |
Use this skill for interactive roder runs that need durable evidence. Prefer the bundled helper script over hand-written tmux commands.
From the repo root:
.agents/skills/roder-tmux/scripts/roder_tmux.sh start
.agents/skills/roder-tmux/scripts/roder_tmux.sh send --enter "summarize this repo"
.agents/skills/roder-tmux/scripts/roder_tmux.sh capture
The default session is roder, the default command is cargo run -p roder-cli --bin roder, and captures go to .roder/tmux-captures/.
roder in a detached tmux session:
.agents/skills/roder-tmux/scripts/roder_tmux.sh start -s roder -- cargo run -p roder-cli --bin roder
.agents/skills/roder-tmux/scripts/roder_tmux.sh start -s roder-dev -- make run
.agents/skills/roder-tmux/scripts/roder_tmux.sh send -s roder "draft a plan"
.agents/skills/roder-tmux/scripts/roder_tmux.sh send -s roder --enter "draft a plan"
.agents/skills/roder-tmux/scripts/roder_tmux.sh keys -s roder Enter C-c
.agents/skills/roder-tmux/scripts/roder_tmux.sh capture -s roder -o .roder/tmux-captures
.agents/skills/roder-tmux/scripts/roder_tmux.sh attach -s roder
.agents/skills/roder-tmux/scripts/roder_tmux.sh stop -s roder
roder or roder-<short-task>.C-c, after every meaningful interaction, and before reporting results..txt and .png paths in the final answer when captures are part of the requested evidence.0.0 in the named session.qlmanage when available, or a Python Pillow renderer if Pillow is installed..txt capture and state that PNG rendering could not run in the current environment.