agentleFS
claudio-atilano-uviclaudio-atilano-uvi/claude-skills/agent-transcript/SKILL.md

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

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.
  • clawsoulsSkill

    discord-clawd

    Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

    Also in 13 projects that use this

  • clawsoulsSkill

    notcrawl

    Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

    Also in 13 projects that use this

  • supermansuper563-opsSkill

    auto-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-botSkill

    discord-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-botSkill

    openclaw-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

  • clawdbotSkill

    openclaw-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

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
  1. Distinctive:

    Never use network. Session discovery reads local agent logs only.

    line 12
  2. Distinctive:

    Never upload raw logs. Render sanitized Markdown first.

    line 13
  3. Distinctive:

    Always ask the user before adding transcript logs to a GitHub PR/issue body.

    line 14
  4. Distinctive:

    Keep user prompts, assistant visible decisions, terse tool summaries, and test/proof outcomes.

    line 19
  5. Distinctive:

    Remove session turns unrelated to the PR/issue work.

    line 20
  6. Very specific:

    Add the ## Agent Transcript section only when inserting a real transcript.

    line 22
  7. Very specific:

    Use a collapsed <details> section and update existing markers instead of duplicating sections.

    line 23
  8. Very specific:

    Run find with title, branch, PR URL/number if known, and cwd.

    line 71
  9. Very specific:

    If a high-confidence session is found, ask: Include a redacted agent transcript?

    line 72
  10. Very specific:

    If the user wants preview, run preview, open the HTML with open, and wait for confirmation.

    line 74
  11. Distinctive:

    Before insertion, trim unrelated session turns from the generated section.

    line 75
  12. Very specific:

    If the user approves, run append-body.

    line 76
  13. Distinctive:

    Use the enriched body file for creation/update.

    line 77
  14. Distinctive:

    If no safe session is found, say nothing and continue without transcript.

    line 78

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 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

.claude/skills/agent-transcript/scripts/agent-transcript --help

Find a likely local session:

.claude/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 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.md

Preview 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.html

Append/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.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:

.claude/skills/agent-transcript/scripts/agent-transcript html \
  --prs /tmp/recent-prs.json \
  --out /tmp/agent-transcript-preview.html

Download now (ZIP)

Does 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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.