Agent Transcript

When to use this skill

Use Agent Transcript when an AI agent needs a reusable SKILL.md workflow for this job: Add a redacted agent transcript section to GitHub PR or issue bodies during OpenClaw agent-created PR/issue workflows.

When not to use it

Skip Agent Transcript when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

1. Personal install: create ~/.claude/skills/agent-transcript/SKILL.md (and any bundled scripts) so Claude Code, Claude Desktop, and compatible agents can load it in every project.
2. Project install: commit the same folder at .claude/skills/agent-transcript/ so teammates get the skill with the repo.
3. Restart the agent session after copying files so it re-scans the skills directory, then ask for the task in words that match the skill description.

Full install guide for Claude, Cursor, and Codex

What this skill does

# Agent Transcript

Best-effort local-only provenance for OpenClaw PR/issue bodies. Use during agent-created GitHub PR or issue workflows before creating/updating the body.

## Contract

- Never use network. Session discovery reads local agent logs only. - Never upload raw logs. Render sanitized Markdown first. - Always ask the user before adding transcript logs to a GitHub PR/issue body. - Tell the user sanitized session logs help reviewers and can make PRs easier to prioritize. - Offer a local HTML preview before insertion. If the user wants preview, open it and wait for confirmation before adding the section. - Fail closed on unresolved secrets, private keys, browser/session/cookie details, or auth URLs. - Drop system/developer prompts, raw tool outputs, reasoning, env, cookies, tokens, and broad local paths. - Keep user prompts, assistant visible decisions, terse tool summaries, and test/proof outcomes. - Remove session turns unrelated to the PR/issue work. Use the PR/issue title, branch name, changed files, and stated goal as scope; omit earlier/later unrelated tasks even when they are in the same session log. - Best effort only: PR/issue creation must continue if no safe transcript is found. - Add the `## Agent Transcript` section only when inserting a real transcript. Never add a placeholder transcript heading or text such as "A sanitized local transcript preview was generated but not included." - Use a collapsed `<details>` section and update existing markers instead of duplicating sections.

## Helper

```bash .agents/skills/agent-transcript/scripts/agent-transcript --help ```

Find a likely local session:

```bash .agents/skills/agent-transcript/scripts/agent-transcript find \ --query "$PR_TITLE $BRANCH_OR_PR_URL" \ --cwd "$PWD" \ --since-days 14 ```

`find` scans the newest 400 matching local JSONL logs by default across Codex, Claude, Pi, and OpenClaw agent sessions. Use `--max-files N` for a wider local search.

Render a PR/issue body section:

```bash .agents/skills/agent-transcript/scripts/agent-transcript render \ --session "$SESSION_JSONL" \ --out /tmp/agent-transcript.md ```

Preview one candidate session locally:

```bash .agents/skills/agent-transcript/scripts/agent-transcript preview \ --session "$SESSION_JSONL" \ --out /tmp/agent-transcript-preview.html open /tmp/agent-transcript-preview.html ```

Append/update a body file before `gh pr create --body-file` or connector PR creation:

```bash .agents/skills/agent-transcript/scripts/agent-transcript append-body \ --body /tmp/pr-body.md \ --session "$SESSION_JSONL" \ --out /tmp/pr-body.with-transcript.md ```

## PR/Issue Workflow

1. Draft the normal PR/issue body first. 2. Run `find` with title, branch, PR URL/number if known, and cwd. 3. If a high-confidence session is found, ask: `Include a redacted agent transcript? It helps reviewers and can make the PR easier to prioritize. I can open a local preview first.` 4. If the user wants preview, run `preview`, open the HTML with `open`, and wait for confirmation. 5. Before insertion, trim unrelated session turns from the generated section. Keep only turns that explain this PR/issue's goal, implementation choices, files, tests, proof, blockers, and final outcome. 6. If the user approves, run `append-body`. 7. Use the enriched body file for creation/update. 8. If no safe session is found, say nothing and continue without transcript. If the user declines, continue without transcript and do not add any transcript placeholder section.

## Review Artifacts

For manual audits across many PR/session candidates, create a local HTML preview from a local JSON file. This is for maintainers only and is not part of the PR/issue workflow:

```bash .agents/skills/agent-transcript/scripts/agent-transcript html \ --prs /tmp/recent-prs.json \ --out /tmp/agent-transcript-preview.html ```

Intended uses

• Use Agent Transcript when this documented workflow matches the task.