Menü
Per-commit trace lineage rows for a branch context, deterministic.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
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.
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.
Take one or more GitHub issues and drive each to a review-ready pull request, holding one belief throughout: an issue is a hypothesis, not a spec. The pipeline VERIFIES BEFORE IT TRUSTS and runs TWO ADVERSARIES before it commits: multi-agent investigation of the real cause (flagging any "landmine" — a cited function or file:line that does not exist) and the blast radius, a plan whose test must go RED BEFORE GREEN, two adversarial gates on that plan (a self/ethos checklist + a pure codex adversarial pass), implementation expressed as a forged `/goal` (via goal-forge) whose verify loop runs the otbox acceptance journey, a green suite + docs sync, a PR that `Closes #<n>`, and a FINAL codex adversarial review of the diff. Honesty, not theater: it reports unmet acceptance criteria and invalid issues rather than faking a fix. The human merges. Everything happens in a per-issue git worktree; multiple issues each get their own worktree + branch + PR. Use when the user says "issue-to-pr", "solve issue", "fix issue #N"
| name | pr-intent-summary-v1 |
| description | Per-commit trace lineage rows for a branch context, deterministic. |
| mode | deterministic-script |
| requires | ["opentraces.core.entity_join","opentraces.core.bursts","opentraces.core.trace_summary","opentraces.core.bucket_store"] |
Emits one structured row per commit on a branch, joining each commit to the agent traces that authored it. The row carries:
lineage array of contributing traces, each with:
Burst.intent.most_substantive_spec)trace_summary.summarize_contribution)ot:// resource pointer + bucket pathno_lineage_reason for commits without trace coverageThis row shape is the endpoint. Any consumer can read it: the PR body
renderer in core.branch_context, a future Slack notifier, a dashboard,
a CI check.
Reads scope from run_packet.json. Expects scope.kind == "branch_context"
with:
{
"kind": "branch_context",
"project_dir": "/abs/path/to/repo",
"project_id": "...",
"base": "main",
"head": "HEAD",
"merge_base": "abc1234...",
"commits": [
{"sha": "...", "short_sha": "abc1234", "subject": "...", "body": "...", "is_merge": false},
...
],
"scope_digest": "..."
}
See schemas/row.schema.json. One JSONL row per commit in scope.commits
order.
python ~/.opentraces/workflows/pr-intent-summary-v1/scripts/build_rows.py
The script reads OT_RUN_PACKET for the run packet and writes rows to
OT_DATASET_OUTPUT. Core lineage fields are deterministic. Optional LLM
polish is on by default for the rendered summary; set OT_LLM_POLISH=0 when a
byte-identical deterministic row stream is required.
opentraces trail blame pr render | create | update — renders the row stream
as a GitHub PR body and (for create/update) pushes via gh.Future consumers can read the same JSONL and project to other destinations without changing this workflow.