agent-transcript
Skill0 starsChanged 4 months agoMITView on GitHub
Add a redacted agent transcript section to GitHub PR or issue bodies during Claude agent-created PR/issue workflows.
- Commits and pushes
15 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- openclaw/agent-skillstheir own version, first seen Nov 8, 2026
- steipete/agent-scriptstheir own version, first seen Oct 20, 2026
- OpenClawAndroid/openclaw-android-assistanttheir own version, first seen Oct 17, 2026
- bighamx/openclaw-android-node-apktheir own version, first seen Oct 9, 2026
- molt-bot/clawdbottheir own version, first seen Oct 8, 2026
- steipete/warelaytheir own version, first seen Oct 8, 2026
Used with
Projects with it also use discord-clawd, notcrawl and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
clawsoulsSkilldiscord-clawd
Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.
Also in 13 projects that use this
clawsoulsSkillnotcrawl
Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.
Also in 13 projects that use this
supermansuper563-opsSkillauto-qa
Continuously audit, live-test, and stress-test the current OpenClaw codebase across at least ten independently scoped subsystem lanes; default to 100 independently verified, landed root-cause fixes, maintain an evidence-backed report, and announce each merged pull request immediately. Use for OpenClaw-wide autonomous QA, live-provider campaigns, gateway, CLI, web, plugin, native-app, scenario, packaging, and extended soak testing.
Also in 11 projects that use this
molt-botSkilldiscord-e2e
Test Discord with Convex-leased QA bots: check credentials without a Gateway, exercise owned messages, or prove OpenClaw replies, files, threads, reactions, streaming, and typing. Distinguish API and Gateway evidence from manual user interactions.
Also in 10 projects that use this
molt-botSkillopenclaw-repair-sweep
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Also in 10 projects that use this
clawdbotSkillopenclaw-performance
Performance work in OpenClaw: a slow or heavy flow (latency, CPU, memory, SQL, RPC, renders), writing or reviewing a perf PR, or adding a cache. Count the work, delete waste first, cache last.
Also in 7 projects that use this
- +2 more from molt-bot
- +3 more from clawsouls
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- clawsouls/soulclaw★ 994% same
- supermansuper563-ops/openclaw-workbench★ 094% same
Wrote their own version · 13
- moltbot/clawdbot★ 394ksame name
- steipete/warelay★ 394ksame name
- steipete/clawdis★ 394ksame name
- moltbot/moltbot★ 394ksame name
- clawdbot/clawdbot★ 394ksame name
- openclaw/openclaw★ 394ksame name
- molt-bot/clawdbot★ 391ksame name
- steipete/agent-scripts★ 7.4ksame name
- openclaw/agent-skills★ 1.1ksame name
- friuns2/openclaw-android-assistant★ 573same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- jiraSkill
- plan-to-jiraSkill
- tempoSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Never use network. Session discovery reads local agent logs only.
- Distinctive: line 13
Never upload raw logs. Render sanitized Markdown first.
- Distinctive: line 14
Always ask the user before adding transcript logs to a GitHub PR/issue body.
- Distinctive: line 19
Keep user prompts, assistant visible decisions, terse tool summaries, and test/proof outcomes.
- Distinctive: line 20
Remove session turns unrelated to the PR/issue work.
- Very specific: line 22
Add the ## Agent Transcript section only when inserting a real transcript.
- Very specific: line 23
Use a collapsed <details> section and update existing markers instead of duplicating sections.
- Very specific: line 71
Run find with title, branch, PR URL/number if known, and cwd.
- Very specific: line 72
If a high-confidence session is found, ask: Include a redacted agent transcript?
- Very specific: line 74
If the user wants preview, run preview, open the HTML with open, and wait for confirmation.
- Distinctive: line 75
Before insertion, trim unrelated session turns from the generated section.
- Very specific: line 76
If the user approves, run append-body.
- Distinctive: line 77
Use the enriched body file for creation/update.
- Distinctive: line 78
If no safe session is found, say nothing and continue without transcript.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Transcript
Best-effort local-only provenance for Claude 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 Transcriptsection 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
.claude/skills/agent-transcript/scripts/agent-transcript --helpFind a likely local session:
.claude/skills/agent-transcript/scripts/agent-transcript find \
--query "$PR_TITLE $BRANCH_OR_PR_URL" \
--cwd "$PWD" \
--since-days 14find scans the newest 400 matching local JSONL logs by default across Codex, Claude, Pi agent sessions. Use --max-files N for a wider local search.
Render a PR/issue body section:
.claude/skills/agent-transcript/scripts/agent-transcript render \
--session "$SESSION_JSONL" \
--out /tmp/agent-transcript.mdPreview one candidate session locally:
.claude/skills/agent-transcript/scripts/agent-transcript preview \
--session "$SESSION_JSONL" \
--out /tmp/agent-transcript-preview.html
open /tmp/agent-transcript-preview.htmlAppend/update a body file before gh pr create --body-file or connector PR creation:
.claude/skills/agent-transcript/scripts/agent-transcript append-body \
--body /tmp/pr-body.md \
--session "$SESSION_JSONL" \
--out /tmp/pr-body.with-transcript.mdPR/Issue Workflow
- Draft the normal PR/issue body first.
- Run
findwith title, branch, PR URL/number if known, and cwd. - 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. - If the user wants preview, run
preview, open the HTML withopen, and wait for confirmation. - 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.
- If the user approves, run
append-body. - Use the enriched body file for creation/update.
- 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:
.claude/skills/agent-transcript/scripts/agent-transcript html \
--prs /tmp/recent-prs.json \
--out /tmp/agent-transcript-preview.htmlDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

