القائمة
Use when sending handoff context from one OpenCode TUI running in tmux to another OpenCode tmux pane, including cross-session context transfer.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/nartc/dotfiles --skill tmux-handoffيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
This skill should be used when the user says "/ship", "commit and push", "create a PR", "ship it", "commit this", "push and PR", or wants to commit, push to remote, and/or create a GitHub pull request. Handles the full commit-push-PR workflow or any subset.
Use when performing git cleanup, staging, committing, branch rewriting, cherry-picking, resetting, cleaning, pushing, force-pushing, or configuring safeguards for destructive git operations.
Commit and ship a branch through Polygraph. Use when the user says "ship for poly", "ship for polygraph", or wants to commit, push branch with Polygraph, set git upstream, and create a PR for the Polygraph session.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | tmux-handoff |
| description | Use when sending handoff context from one OpenCode TUI running in tmux to another OpenCode tmux pane, including cross-session context transfer. |
Use this skill to prepare and paste a compact handoff from the current opencode session into another opencode session running in a different tmux pane.
Default behavior: paste into the target pane for user review. Do not press Enter or auto-submit.
handoff content format: objective, current state, decisions/constraints/invariants, files/sources, verification evidence, risks, acceptance criteria, suggested skills, and next prompt.%12 or a tmux target like session:window.pane.send-keys.Use the portable handoff structure, then paste it via tmux. Minimum structure:
# Handoff
## Objective
- ...
## Current state
- ...
## Decisions / constraints / invariants
- ...
## Files / locations / sources
- `path`: why it matters
## Verification evidence
- `command`: result summary
- Not run: checks intentionally not run and why
## Open questions / risks
- ...
## Acceptance criteria / done state
- ...
## Suggested skills / agents
- ...
## Next prompt
Continue from this handoff. First verify the referenced files/state, then proceed with: ...
Keep the note compact. Prefer durable facts over transcript dump. Include exact file paths, branch/repo/workdir if relevant, and anything the next session must not repeat.
Run:
tmux list-panes -a -F '#{pane_id}\t#{session_name}:#{window_index}.#{pane_index}\t#{pane_current_command}\t#{pane_current_path}'
Prefer panes where pane_current_command looks like opencode, node, bun, or the user clearly identifies it. If unsure, ask.
Use paste-buffer -p so tmux sends bracketed-paste markers.
tmpfile="$(mktemp -t opencode-handoff.XXXXXX.md)"
Then write the handoff note to $tmpfile using the file editing tool, not heredoc.
Then paste and clean up:
tmux load-buffer -b opencode-handoff "$tmpfile" && tmux paste-buffer -p -b opencode-handoff -t "$TARGET_PANE" && rm -f "$tmpfile"
After paste, ask whether to submit with Enter; only run tmux send-keys Enter after explicit user confirmation.
Report: