Skip to content

majiayu000/spellbook / skills/codex-fluent

codex-fluent

Verified

Use when Codex feels slow, bloated, or heavy after heavy use. Provides safe session hygiene, archive strategy, and handoff discipline to keep daily Codex usage responsive and low-friction. Always pairs with comprehensive handoffs before archiving active work.

references/maintenance-checklist.md

View on GitHub
# Codex Fluent — Safe Maintenance Checklist

Use this checklist when running `codex-fluent` in apply mode. Treat every step as mandatory unless you have a very good reason.

## Pre-Apply (Do This Every Time)

- [ ] Ran full diagnosis in report mode first
- [ ] Reviewed sizes and candidates
- [ ] Identified all active repo chats that still matter
- [ ] Created high-quality handoff documents + reactivation prompts for every chat you might want to continue later (see handoff-template.md)
- [ ] Confirmed Codex is not running (or explicitly accepted `--wait-for-codex-exit`)
- [ ] Understand that we only archive, never delete

## Backup Phase

- [ ] Triggered a timestamped backup (the skill does this automatically in apply mode)
- [ ] Know where the backup lives: `~/Documents/Codex/codex-backups/codex-fluent-...`
- [ ] (Optional but recommended) Manually copy the backup to an external drive for very large cleanups

## Archive Decisions

For each candidate the report surfaced, explicitly decide:

- [ ] This session/chat → archive (only after handoff exists)
- [ ] This worktree → archive (stale and not needed)
- [ ] This log → rotate/archive
- [ ] This config entry → safe to prune

## During Apply

- [ ] Skill is running with appropriate flags (usually `--archive-older-than-days X --worktree-older-than-days Y`)
- [ ] Watching for any warnings

## Post-Apply Verification

- [ ] Ran diagnosis again
- [ ] Confirmed active state is now significantly smaller
- [ ] Started a fresh test thread to verify "snappy" feel
- [ ] Can still find and read all archived material if needed
- [ ] (If using the optional metadata repair) Verified that full transcripts are still intact

## After First Successful Maintenance

- [ ] Asked the skill to generate a recurring **report-only** reminder prompt
- [ ] Scheduled it (weekly for heavy use, bi-weekly otherwise)
- [ ] Documented your personal policy (e.g. "archive non-pinned chats older than 10 days after handoff")

## Red Flags — Stop and Re-evaluate

- You feel pressure to archive something without a handoff "just this once"
- The skill suggests touching credentials or global skills you still actively use
- You haven't used the resulting handoff documents in practice yet (they might need improvement)
- Active state is still huge after archiving (there might be other causes — database bloat, many open sidebar threads, etc.)

Remember the goal: **Codex should feel like a sharp, lightweight tool again**, not a heavy application you have to fight. Handoff discipline is what makes aggressive archiving safe.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall