agent-transcript

To attach agent session logs to a GitHub PR, you can parse local agent JSONL logs and generate a sanitized Markdown transcript. This skill appends the redacted summary directly to the pull request body for human reviewers.

Sanitizing sensitive data from agent JSONL logs requires automated redaction to strip tokens, cookies, and private paths. The process extracts relevant session turns while filtering out unrelated tasks to ensure secure provenance.

Providing transparency for agent-created pull requests involves generating a structured Markdown summary of agent decisions and tool usage. This gives reviewers contextual insight into the agent logic without exposing raw logs.

Yes, you need local access to agent JSONL logs to generate PR transcripts. This skill operates entirely within the local development environment to parse sessions and filter out sensitive system data before formatting outputs.

Yes, you can use PR automation to document agent reasoning by appending a redacted transcript to the PR body. This allows human reviewers to quickly verify the agent testing steps and logic during code reviews.

Raw agent logs are unsuitable for direct GitHub issue attachment because they contain sensitive system data, tokens, and unrelated tasks. Sanitizing and extracting relevant turns ensures only redacted, human-readable context is shared.