skills/deprecated/atuin-history-cleanup/SKILL.md
Use when auditing Atuin shell history for noisy duplicates or high-confidence typo/retry pairs and when preparing safe preview-first cleanup steps without editing the SQLite database directly.
npx skillsauth add narumiruna/agent-skills atuin-history-cleanupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Audit first, delete second. Use the bundled script to summarize duplicate pressure and high-confidence typo-like retries. For typo cleanup, prefer the transactional cleanup-typos command so the flow snapshots history.db, uploads the current host history store, deletes candidates, verifies the result, and rolls back automatically if verification fails.
Read references/atuin-cli.md when you need the exact delete, dedup, or prune behavior.
history.db before removing anything.atuin history dedup would remove while still keeping the newest repeated entries.gti status followed by git status.atuin info and the audit script before any destructive step.atuin history dedup is not a single-command delete tool.atuin search --delete is query-wide and follows Atuin's active search semantics. Do not use it manually for typo cleanup.cleanup-typos is the only approved automation path for typo deletion. It may use atuin search --delete only after a strict uniqueness gate; any ambiguous match must fall back to the interactive inspector path.cleanup-typos must snapshot history.db before deletion and delay the final remote sync until verification passes.history_filter and cwd_filter tuning is out of scope for v1.atuin info
uv run python skills/deprecated/atuin-history-cleanup/scripts/atuin_history_cleanup.py audit
Useful flags:
uv run python skills/deprecated/atuin-history-cleanup/scripts/atuin_history_cleanup.py audit --db-path ~/.local/share/atuin/history.db --dupkeep 3 --before now --typo-window-seconds 300 --max-typos 20
Review the duplicates section first.
Use the reported atuin history dedup --dry-run ... command. If the dry run matches expectations, rerun the same command without --dry-run.
Review the typos section second and choose one path:
Preferred transactional path:
uv run python skills/deprecated/atuin-history-cleanup/scripts/atuin_history_cleanup.py cleanup-typos
Useful flags:
uv run python skills/deprecated/atuin-history-cleanup/scripts/atuin_history_cleanup.py cleanup-typos --db-path ~/.local/share/atuin/history.db --before now --typo-window-seconds 300 --max-typos 20 --backup-dir ~/.local/share/atuin/cleanup-backups/manual-run
Manual review path:
Start with the suggested atuin search -i --search-mode prefix ... preview command. The audit will also add --cwd <cwd> when it knows the original working directory, so review stays narrow even if your default Atuin config uses skim or another fuzzy mode. In the TUI inspector, use Ctrl+O, confirm the exact entry, then Ctrl+D to delete that one row.
atuin info unless --db-path is provided.id, timestamp, exit, command, cwd, session, and hostname.(command, cwd, hostname) and reports how many rows exceed --dupkeep.--search-mode prefix override and never emits atuin search --delete.cleanup-typos first runs the same typo audit, then creates a snapshot, writes pre_audit.json, plan.json, and post_verify.json, and only commits the deletion to remote sync after verification succeeds.duplicates gives one global preview/apply pair for history dedup.typos gives per-row review data: id, time, cwd, original command, suggested correction, reason, and shell-safe preview commands for inspector review only.--format json is preferable when another tool needs to post-process the audit.cleanup-typos prints a text summary and leaves its backup and verification artifacts in the chosen backup directory.development
Maintains concise repository MEMORY.md notes for gotchas, stale memory corrections, and durable user preferences. Use at the start of repository conversations, when the user mentions MEMORY.md, when an error should be remembered to avoid repeating it, or when MEMORY.md content may be wrong.
testing
Use only when the user explicitly names the work-log-writer skill; never auto-activate from generic work log, daily log, EOD summary, status update, or date-range summary requests.
development
Use when implementing non-trivial code changes that should follow TDD (write a failing test first, make the smallest passing change, then refactor safely).
tools
Use when designing, implementing, reviewing, or debugging Codex CLI hooks, including `hooks.json`, `.codex/hooks.json`, feature-flag setup, matcher behavior, event-specific stdin/stdout payloads, and hook scripts for `SessionStart`, `PreToolUse`, `PostToolUse`, `UserPromptSubmit`, or `Stop`.