解决更改codex provider后导致的对话记录消失的问题
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Codex
Model
Multiple
Fastest way to find out if codex-provider-history-repair-skill belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/Departure-love/codex-provider-history-repair-skillRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/Departure-love/codex-provider-history-repair-skillNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ codex-provider-history-repair-skill/ ← installs here └─ settings.json
解决更改codex provider后导致的对话记录消失的问题