codoc:share
Share a file for collaborative editing with a human via browser. Use when the user wants to collaboratively edit a markdown file, get feedback, or have a conversation within a document.
- License 许可
- MIT
- 最近更新
- 2026-05-19
- Stars
- ★ 27
- Forks
- 5
01 前言 Front Matter
- name
- codoc:share
- description
- Share a file for collaborative editing with a human via browser. Use when the user wants to collaboratively edit a markdown file, get feedback, or have a conversation within a document.
02 资源文件 3
- 其他customize.toml1.7 KB
- 资产文件solving-methods.csv7.1 KB
- 参考文档template.md2.0 KB
03 SKILL.md 正文
Share File for Collaborative Editing
Flow
-
codoccli should already be installed on the machine. Just callcodoc xxxwithout any prefixes! -
Run
codoc serverin background (setrun_in_background: true, timeout 600000ms). This starts the HTTP server and tunnel. It blocks until killed — that's expected. -
codoc share /absolute/path/to/file.md→ prints Edit URL + Readonly URL + token. No need to wait - this command will wait for the server to be ready. -
Tell user the Edit URL (or Readonly URL if they should only view)
-
Run
codoc poll <token> agentin background (setrun_in_background: true, timeout 600000ms). You will be notified when the human edits. Continue with other work while waiting. -
When poll completes, read the file. Find
[REPLY_TEMPLATE]lines inside<!-- ... -->blocks, replace each with your reply (keep the line format, remove[REPLY_TEMPLATE]prefix). -
Run
codoc poll <token> agentin background again. Repeat 4-5. -
When you have nothing else to do, keep polling. Only stop polling if the user gives you a different task.
Troubleshooting
If the user says the link doesn't work, is broken, or returns 404:
- Try
codoc shareagain on the same file to get a fresh URL. - If re-share fails (server not running), stop the old background
codoc servertask (via TaskStop orcodoc stop), then restart from step 1 of the Flow (runcodoc serverin background, thencodoc share).
Comment Block Format
A comment block applies to the line immediately above it — place your comment right after the line you want to discuss.
Comments are grouped in multi-line blocks:
<!--
@user[cid:abc]: question here
[REPLY_TEMPLATE] @agent[cid:def][reply:abc]: your response here (use \n for newlines)
-->
To reply, replace the [REPLY_TEMPLATE] line with:
@agent[cid:def][reply:abc]: your actual response
Escape --> as \-\-\>, newlines as \n within comment text.
Remote Access
bash <(curl -sf <server-url>/codoc.sh) edit <token> <author>
bash <(curl -sf <server-url>/codoc.sh) poll <token> <author>
bash <(curl -sf <server-url>/codoc.sh) who <token>
04 同仓库更多 Skills
verifier
E2E test verifier workflow.
spec-to-code
Implement a spec into working code, one plan step at a time.
spec-gen
Generate a complete specification from a rough idea through interactive requirements gathering, research, design, and implementation planning.
spec-driven
End-to-end pipeline from rough idea to merged pull request. Passing --quick forwards the flag to the spec-gen sub workflow.
release
General release workflow for GitHub projects.
pr-lifecycle
Monitor a PR/MR until it is merged or closed.