菜单
Keep nontrivial Punaro work isolated from main.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Safely send or receive one explicit Punaro v3 attachment through the locally provisioned controller. Use for a typed offer whose body has the exact `punaro/attachment-offer/v3:` marker, or when the task owner explicitly authorizes one pre-provisioned local file transfer.
Receive and safely handle messages delivered through a local Punaro-connected agent-mailbox. Use when an agent must await incoming mail, inspect a Punaro typed envelope, acknowledge a completed delivery, or diagnose a local mailbox wake-up without changing relay enrollment or routing.
Reply to a message delivered through Punaro or agent-mailbox using the conversation ID in its typed envelope. Use when an agent receives application/vnd.punaro.message+json, a user asks for a reply through an existing Punaro conversation, or a Telegram-routed agent request needs a durable response.
Monitor a Punaro pull request until checks, reviews, and merge are complete.
| name | using-git-worktree |
| description | Keep nontrivial Punaro work isolated from main. |
Adapted from Spectre's worktree workflow for this Go repository.
Before changing tracked files, inspect git worktree list and the current
branch. If already on a non-main worktree, keep using it. Otherwise create a
descriptive agent/<feature> branch from main in an ignored local worktree
directory, then run make test before editing. Never create a feature branch
in a dirty main checkout.
Before pushing from a worktree, run the full Punaro gate:
make test
make test-race
make staticcheck
make security
make lint
After a merged PR, switch the primary checkout to main, remove the feature
worktree, and delete only the local feature branch.