菜单
Sync both git repos in this project: opentraces (root) and closedtraces (kb/). Runs the full lifecycle for each — pull, check status, commit any pending changes, push. Use when the user says "gitsync", "sync repos", "sync both repos", "commit and push both", or "sync opentraces and closedtraces".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Share agent traces to open datasets on HuggingFace Hub. Use this skill when the user mentions OpenTraces, trace capture, Trace Trails, workflow-built datasets, dataset review, or publishing reviewed dataset rows.
Share agent traces to open datasets on HuggingFace Hub. Use this skill when the user mentions OpenTraces, trace capture, Trace Trails, workflow-built datasets, dataset review, or publishing reviewed dataset rows.
Project already-captured traces into scored-rollout rows for the SkillOpt optimizer.
Per-commit trace lineage rows for a branch context, deterministic.
Derive compact eval rows from command-attributed trace trajectories.
Land every site-related fix on main, deploy opentraces.ai to Vercel production, and verify it works across all pages (desktop + mobile) and the email-capture flow, fixing and re-deploying until green. Runs as a goal: land -> deploy -> verify -> triage -> repeat until safe. Use when the user says "deploy site", "deploy to vercel", "push site", "ship the site", "deploy-site", or "land and verify the site". For a full coordinated release that also bumps the version and publishes the Python packages, use /release-pack instead.
| name | gitsync |
| description | Sync both git repos in this project: opentraces (root) and closedtraces (kb/). Runs the full lifecycle for each — pull, check status, commit any pending changes, push. Use when the user says "gitsync", "sync repos", "sync both repos", "commit and push both", or "sync opentraces and closedtraces". |
Sync both repos in this project: opentraces (root) and closedtraces (kb/).
| Repo | Path | Remote |
|---|---|---|
| opentraces | /Users/jayfarei/src/tries/2026-03-27-community-traces-hf | github.com/JayFarei/opentraces |
| closedtraces | /Users/jayfarei/src/tries/2026-03-27-community-traces-hf/kb | github.com/JayFarei/closedtraces |
git -C <path> pull --rebase
If the pull produces a merge conflict, stop immediately and report it to the user with the conflicted files. Do not attempt to resolve conflicts automatically.
git -C <path> status --short
If clean, skip to the next repo — nothing to commit.
Show the user a brief summary of what's pending (file list + diff stat), then commit:
git -C <path> add -A
git -C <path> commit -m "$(cat <<'EOF'
<descriptive message summarizing the changes>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
EOF
)"
Write a meaningful commit message. Do not use generic messages like "sync" or "update files".
Look at git diff --cached to understand what changed and summarize it.
git -C <path> push
If push is rejected (non-fast-forward), pull --rebase first then push again.
After completing both repos, report a one-liner per repo:
opentraces: pulled (2 commits), committed "fix(quality): ..." (3 files), pushed
closedtraces: already up to date, committed "update discussion log" (1 file), pushed
Or if nothing needed:
opentraces: already up to date, nothing to commit
closedtraces: already up to date, nothing to commit