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/handoff-template.md
View on GitHub# Codex Handoff Document Template
Use this structure when creating a handoff before archiving a valuable session with `codex-fluent`.
The goal of a handoff is **perfect continuity with minimal context**. A fresh Codex thread (or even Claude via the `codex` skill) should be able to read the repo + this document and continue productively without the old chat.
---
**Project / Ticket:**
**Date of Handoff:**
**Previous Session Context (optional):**
**Handoff Author:** (usually Codex itself)
## Executive Summary (2-4 sentences)
What we were trying to achieve and the current state.
## Key Decisions & Rationale
- Decision: ...
- Rationale: ...
- Tradeoffs considered: ...
## Current Codebase State
List only the files that matter for continuation. One line each.
- `path/to/important/file.ts`: Current purpose + recent changes
- ...
## Environment & Commands
- How to run / test / build relevant parts
- Any special setup or env vars for this task
## What Has Been Completed
- [x] ...
- [x] ...
## Open Questions & Next Steps (Prioritized)
1. **High** — Specific task with clear success criteria
2. **Medium** — ...
3. **Low / Nice to have** — ...
## Constraints & Preferences (Very Important)
- Do not touch: ...
- User style notes: (e.g. "prefers early returns", "hates magic numbers in this file")
- Things we deliberately avoided and why
## Reactivation Prompt (Copy-Paste Ready)
```
We are continuing work from a previous Codex session.
Read the handoff document at: docs/codex-handoffs/YYYY-MM-DD-topic.md (or wherever it was saved).
1. First, explore the current state of the repo to verify what still applies.
2. Read the handoff document completely.
3. Then continue from the "Open Questions & Next Steps" section.
4. Do not assume the previous chat history is available.
Start by confirming you have understood the current state and the next priority.
```
## Additional Notes for Future You
Anything that might be useful 2 weeks or 2 months from now.
---
**Save this file** in a stable location, for example:
- `docs/codex-handoffs/YYYY-MM-DD-short-topic.md`
- Or a project-specific handoff directory you already use.
After saving, you can safely archive the original heavy session using `codex-fluent`.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: 472k | 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 |