application security (OWASP
STRIDE threat modeling) and code architecture
Agent skill for agent-transcript
Loading actions...
STRIDE threat modeling) and code architecture
param2: value2)'
capitalization
Best-effort local-only provenance for OpenClaw PR/issue bodies. Use during agent-created GitHub PR or issue workflows before creating/updating the body.
render or append-body produced it.## 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."<details> section and update existing markers instead of duplicating sections.skills/agent-transcript/scripts/agent-transcript --help
Find a likely local session:
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.
In a downstream repo that syncs shared skills under .agents/skills, replace
skills/agent-transcript with .agents/skills/agent-transcript.
Render a PR/issue body section:
skills/agent-transcript/scripts/agent-transcript render \
--session "$SESSION_JSONL" \
--out /tmp/agent-transcript.md
Preview one candidate session locally:
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:
skills/agent-transcript/scripts/agent-transcript append-body \
--body /tmp/pr-body.md \
--session "$SESSION_JSONL" \
--out /tmp/pr-body.with-transcript.md
find with title, branch, PR URL/number if known, and cwd.Include a redacted agent transcript? It helps reviewers and can make the PR easier to prioritize. I can open a local preview first.preview, open the HTML with open, and wait for confirmation.## Agent Transcript section before showing it to the user or inserting it publicly. Keep only turns that explain this PR/issue's goal, implementation choices, files, tests, proof, blockers, and final outcome.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:
skills/agent-transcript/scripts/agent-transcript html \
--prs /tmp/recent-prs.json \
--out /tmp/agent-transcript-preview.html