解决更改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.
You can test this quickly and remove it cleanly if it misses.
GitHub health 28/100. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Universal
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.
git clone https://github.com/Departure-love/codex-provider-history-repair-skill && cd codex-provider-history-repair-skill && cat README.mdRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf codex-provider-history-repair-skillNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
./ └─ codex-provider-history-repair-skill/ ← clones here
解决更改codex provider后导致的对话记录消失的问题
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 10, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.