majiayu000/spellbook / skills/codex-fluent
codex-fluent
VerifiedUse 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.7 KB |
| references/examples/handoff-quality-example.md | markdown | 1.8 KB |
| references/examples/typical-before-after.md | markdown | 1.5 KB |
| references/handoff-template.md | markdown | 2.2 KB |
| references/maintenance-checklist.md | markdown | 2.5 KB |
references/examples/typical-before-after.md
View on GitHub# Example: Typical Before/After Report (Anonymized)
## Before (Heavy Use for 6 Weeks)
- Active sessions: ~47 GB total (many long debugging threads + old feature work)
- Largest active chat: 8.2 GB (one particularly painful auth + infra incident)
- Stale worktrees: 14 (some over 3 weeks old)
- Large logs: several `logs_2.sqlite*` files > 1.2 GB each
- Thread metadata bloat detected: 3 threads with title/preview > 80k characters each
- Feeling: "Codex takes 12–15 seconds to start and feels heavy when switching anything"
## Actions Taken
1. Created handoff documents for the 4 active repos the user actually cared about continuing.
2. Archived 38 old sessions (everything non-pinned older than 12 days after handoffs).
3. Moved 11 stale worktrees.
4. Rotated oversized logs.
5. Cleaned dead project entries in config.
## After (Same Day)
- Active sessions: 2.8 GB (mostly current 2–3 active threads)
- Archived sessions: 41 GB (still fully accessible, just not loaded)
- Startup time: subjectively "instant" again
- Switching between current threads: fast and pleasant
- Mental load: much lower — user knows exactly which work is "hot" and which is safely in handoff + archive
## Key Lesson
The 8 GB incident thread was archived after a 40-minute handoff document was written. Two weeks later the user needed to look something up from it — they used the handoff + quick `grep` in the archived transcript instead of reopening the giant chat. Much better experience.
This pattern repeated across multiple cleanups.Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 471k | Updated | Claude CodeCodex | Verified | Install |
| 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: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |