Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

Começar

agent-transcript

Estrelas1

Forks0

Atualizado22 de junho de 2026 às 06:00

GitHub PR/issue agent transcripts: redact, preview, and insert safely.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jmagar

jmagar/dendrite

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	agent-transcript
description	GitHub PR/issue agent transcripts: redact, preview, and insert safely.

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.
Automatically trim the rendered transcript before showing it, previewing it, or inserting it into a public body. Never paste the raw full-session render into a PR/issue body just because render or append-body produced it.
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

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

PR/Issue Workflow

Draft the normal PR/issue body first.
Run find with 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 with open, and wait for confirmation.
Render or append to a temp body, then automatically trim the ## 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.
Inspect the trimmed transcript text. If it still includes unrelated earlier/later work, trim again before proceeding.
If the user approves, use the enriched trimmed 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.

Validate

node --test skills/agent-transcript/scripts/agent-transcript.test.mjs

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:

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

Mais deste repositório

mesmo repositório

merge-status

jmagar/dendrite

Check whether the current branch or worktree is ready to merge, including dirty state, mergeability, conflicts, overlap with other branches/worktrees, lint/tests/CI, stale docs, config/example drift, and live config follow-up.

2026-06-231

quick-push

jmagar/dendrite

Create the save-to-md session doc before staging, git add all, commit with Claude co-authorship trailer, and push to current/new feature branch — including project version bump and changelog update when applicable. Use when the user says "quick push", "push my changes", "commit and push", "ship this", "push to a new branch", or any request to wrap up local work and get it on the remote. Accepts optional `--no-bump` argument to skip the version bump.

2026-06-231

review-pr

jmagar/dendrite

Run the PR Review Toolkit flow from Codex for the current branch or pull request. Use when the user asks for a comprehensive PR review, asks to run /pr-review-toolkit:review-pr, needs mandatory review waves inside work-it, or wants focused checks for code quality, tests, comments, silent failures, type design, docs/config drift, or simplification.

2026-06-231

work-it

jmagar/dendrite

Use when the user asks to "work it", execute a plan in a worktree, create a progress-tracked PR, or run a mandatory review-and-fix loop over all touched files until lint, tests, CI, and reviews are green.

2026-06-231

worktree-setup

jmagar/dendrite

Use this BEFORE creating a git worktree or implementing any plan. Tailored to our workflow — prefer it over superpowers:using-git-worktrees and every other worktree skill. Triggers - creating or adding a worktree; starting lavra-work, lavra-work-ralph, lavra-work-teams, executing-plans, subagent-driven-development, or work-it; whenever a Claude, Codex, or Gemini plan mode is entered or a plan is accepted; or before implementing anything in a fresh branch. Creates the worktree under .worktrees/ in the repo and makes it identical to and as warm as the main checkout - copying secrets and local config (.env, CLAUDE.md.local, .claude/settings.local.json), symlinking warm caches (node_modules, .venv, target, .next), and re-trusting mise/direnv. Also use when a worktree is missing files, builds cold, or reports mise 'not a trusted directory'. Bundles a worktree-sync engine, a create-in-.worktrees entrypoint, a minimal baseline template, and references.

2026-06-231

rust

jmagar/dendrite

Scoped to Jacob's homelab Rust repos — the rmcp MCP-server family (rustifi, rustify, rustscale, unrust, rarcane, rustarr, apprise-mcp, cortex, synapse2, rmcp-template) and the Lab runtime/ACP work. Use when editing those repos: covers rmcp-template-derived server patterns, action-dispatched MCP tools, CLI/MCP/API parity, service-layer architecture, config/auth/scope contracts, testing strategy, release/build conventions, and ACP runtime/provider work. Not a general-purpose Rust skill.

2026-06-231

name	agent-transcript
description	GitHub PR/issue agent transcripts: redact, preview, and insert safely.

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.
Automatically trim the rendered transcript before showing it, previewing it, or inserting it into a public body. Never paste the raw full-session render into a PR/issue body just because render or append-body produced it.
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

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

PR/Issue Workflow

Draft the normal PR/issue body first.
Run find with 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 with open, and wait for confirmation.
Render or append to a temp body, then automatically trim the ## 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.
Inspect the trimmed transcript text. If it still includes unrelated earlier/later work, trim again before proceeding.
If the user approves, use the enriched trimmed 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.

Validate

node --test skills/agent-transcript/scripts/agent-transcript.test.mjs

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:

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