Menu
Manage restore context files so skills can survive /clear and /compact. Use to write, delete, check, or list .agent-restore-context-* files.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | agent-restore-context |
| description | Manage restore context files so skills can survive /clear and /compact. Use to write, delete, check, or list .agent-restore-context-* files. |
| disable-model-invocation | false |
| argument-hint | <action> [<skill-name>] [-- <content>] |
| allowed-tools | Bash, Grep, Glob, Read, Edit, Write |
| scope | ["knowledge"] |
Manage .agent-restore-context-<skill-name> files in the project root. These
files are automatically injected into context after /clear or /compact by
a SessionStart hook, allowing skills to resume where they left off.
action (required): One of write, delete, check, or statusskill-name (required for write/delete): The skill name used as the file suffixcontent (required for write): The full prompt content to inject after a
context reset. Delimited by -- — everything after -- is treated as content./agent-restore-context write jira-implement-task -- === RESUMED ... — create
or overwrite a restore context file; everything after -- is the content/agent-restore-context delete jira-implement-task — remove the file when
the workflow is complete/agent-restore-context check — verify the hook is set up, offer to install
if not/agent-restore-context status — list all active restore context filesRead .claude/settings.json and .claude/settings.local.json (if it exists).
Search both for restore-context. If not found:
check, invoke /agent-restore-context-setup and stop./agent-restore-context-setup first. Do not proceed
with write until the hook is confirmed.write <skill-name>Parse $ARGUMENTS: split on the first -- separator. Before it is the
action and skill-name; everything after it is content.
Write .agent-restore-context-<skill-name> to the project root with the
parsed content (creates or overwrites). The content should be a complete,
self-contained prompt that tells the model how to resume. Recommended
structure (callers may use any format):
=== <SKILL-NAME> — RESUMED AFTER CONTEXT RESET ===
<Key state: ticket, branch, current task, etc.>
You MUST do the following before any other work:
1. Invoke /<skill-name> <arguments> to reload the full skill instructions.
2. <Read relevant plan/state files>
3. <Read relevant source/test files>
4. Continue from where you left off.
Do NOT start any work until you have completed the above steps.
=== END RESUMED CONTEXT ===
Confirm the file was written and its path.
delete <skill-name>.agent-restore-context-<skill-name> from the project root.check.agent-restore-context-* files in the project root./agent-restore-context-setup.status.agent-restore-context-* files in the project root..agents/ directories — only use them if they already existAgent restore context: $ARGUMENTS
Set up the restore-context hook so skills can resume workflows after /clear and /compact. Use when setting up a new project or after cloning a repo that uses restore-context skills.
Fetch Jira ticket, create branch, implement changes, commit, push, open PR.
Generate AI-assisted navigation aids to help humans start reviewing a pull request more efficiently. Use when starting a PR review to get oriented on large or unfamiliar changes.
Persist guidelines, conventions, and architectural decisions into the repository's knowledge base. Use when told to remember something for future sessions.
Perform migrations for Renovate dependency upgrades based on breaking changes identified in a review. Use after running /renovate-review.
Review Renovate dependency upgrade PRs to assess safety and effort. Use when reviewing PRs from Renovate bot that update NPM dependencies.