AGENT SKILL

transcript-retention

Use to manage the disk footprint of AI-tool session state — Claude Code transcripts (~/.claude/projects), Codex rollouts (~/.codex/sessions), shell snapshots, logs, and sqlite WAL files — by reporting usage and applying an age-based compress/delete policy. Triggers: "how big is my session history", "clean up old transcripts", "codex sessions are eating disk", "transcript retention".

License 许可
MIT
最近更新
2026-11-10
Stars
★ 0
Forks
0

01 前言 Front Matter

name
transcript-retention
metadata
{ "owner": "tze", "status": "active", "authors": [ "tze", "Claude Fable 5" ], "last_reviewed": "2026-06-12" }
description
Use to manage the disk footprint of AI-tool session state — Claude Code transcripts (~/.claude/projects), Codex rollouts (~/.codex/sessions), shell snapshots, logs, and sqlite WAL files — by reporting usage and applying an age-based compress/delete policy. Triggers: "how big is my session history", "clean up old transcripts", "codex sessions are eating disk", "transcript retention".
compatibility
Linux/macOS with gzip and standard find; assumes ~/.claude and ~/.codex tool homes.

03 SKILL.md 正文

Transcript Retention

Session stores grow without bound (observed 2026-06-12: ~/.codex/sessions 3.4G, ~/.claude/projects 700M). But transcripts are not junk: they are the data source for ../audit-skill-hygiene/SKILL.md and for any future usage analytics. Retention policy therefore defines the maximum audit window — decide retention with that trade-off, never as plain disk cleanup.

Inventory first (always safe)

du -sh ~/.claude/projects ~/.codex/sessions ~/.codex/shell_snapshots \
       ~/.codex/log ~/.codex/tmp 2>/dev/null
# Age profile: bytes per month
find ~/.codex/sessions ~/.claude/projects -name "*.jsonl" -printf "%TY-%Tm %s\n" 2>/dev/null \
  | awk '{b[$1]+=$2} END {for (m in b) printf "%s  %6.0f MB\n", m, b[m]/1e6}' | sort

Report the inventory and the proposed action per tier before touching anything.

Default policy (adjust per user preference)

Age Action Rationale
< 60d keep as-is active audit window, resumable sessions
60–180d gzip in place ~10x smaller; still grep-able via zgrep for audits
> 180d propose deletion beyond any realistic audit window
  • Compression is safe and reversible; deletion is destructive — always list the candidates (count + size + date range) and get explicit confirmation before rm.
  • Never touch files modified in the last 7 days regardless of policy: an active session's transcript may have an old creation date.
  • ~/.codex/tmp and rotated logs are exempt from the confirmation rule (genuinely disposable), but report what was reclaimed.

Hard stops

  • Do not delete or compress sqlite databases or their -wal/-shm sidecars (goals_*.sqlite, memories_*.sqlite, state_*.sqlite) — they are live state, not history, and a WAL file belongs to its DB.
  • Do not prune transcripts younger than the longest audit window the user relies on; if unsure, ask before the delete tier (compress tier is fine).
  • If a zgrep-based audit has never been exercised after the first compression pass, run one spot-check (zgrep -c '"name":"Skill"' on a compressed file) and note that audit tooling must use zgrep/zcat for the compressed tier.

04 同仓库更多 Skills

tzeusy-org
tzeusy-org/ai-bootstrap

user-run

Use when a step needs privileges this session lacks (docker, sudo, another user's checkout or secrets, host access) and the owner must run it as tze. Writes a reviewable /home/orca/.tmp/<slug>/run.sh that impersonates tze (USER_TO_IMPERSONATE overrides), tees timestamped logs plus latest.log and collects artifacts there; Claude presents it with a risk and time brief, then continues from the logs. Triggers: "I'll run it for you", "permission denied on docker.sock", "needs sudo", "sudo: a password is required", "run as tze", "/user-run".

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

开发工程师代码审查
★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

开发工程师代码审查
★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

★ 0
tzeusy-org
tzeusy-org/ai-bootstrap

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

★ 0