Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sakurabytecore/context-recovery
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.
Passed 19 of 22 test cases with the skill, and 11 of 22 without it.
and 11 more in the full report
10 fixed11 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am querying local agent sessions for issue #142, but my local log directory contains data from multiple repositories. Which flag isolates the search to the `mobile-app` project directory when calling `scripts/search_sessions.py`?
| Checked | Without skill | With skill |
|---|---|---|
| Uses --path-filter mobile-app to constrain the search path. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill to build an evidence-first project handoff brief from local agent sessions. It is not semantic memory or a live GitHub source of truth. It works best with hard identifiers: owner/repo, branch names, file paths, commit hashes, exact errors, PR/issue numbers plus repo filters, or unique commands.
Old sessions are historical evidence. Mutable facts such as PR state, CI, releases, deployments, and current files still require live checks before action.
Generate a context brief first. Resolve scripts/search_sessions.py relative to this skill directory; after npm installation the full package path is node_modules/codexmate/skills/context-recovery/scripts/search_sessions.py.
python3 scripts/search_sessions.py "SakuraByteCore/codexmate feat/task-orchestration-tab" --mode brief --source all --path-filter codexmate --match all --format text --limit 8
Use plain search when you need raw candidates:
python3 scripts/search_sessions.py "exact error text" --mode search --source all --path-filter codexmate --format text --limit 10
owner/repo, short repo name, PR/issue number with repo filter, branch, file path, commit hash, exact error, then user wording.--mode brief; add --path-filter for project/worktree isolation; use --match all when the query has strong identifiers.high means multiple hard signals appeared; medium/weak means re-query with stronger identifiers before relying on it; none means no hits were found.test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.