Help us improve
Share bugs, ideas, or general feedback.
From popkit-dev
Restores full project context from previous sessions by loading STATUS.json, reviewing git status/commits/diffs, reading key files, running tests/lint/build, and rebuilding mental model. Use after breaks, not for quick tasks.
npx claudepluginhub jrc1883/popkit-ai --plugin popkit-devHow this skill is triggered โ by the user, by Claude, or both
Slash command
/popkit-dev:pop-context-restoreThe summary Claude sees in its skill listing โ used to decide when to auto-load this skill
Fully restore working context when resuming after a break. Goes beyond STATUS.json to rebuild complete understanding.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Fully restore working context when resuming after a break. Goes beyond STATUS.json to rebuild complete understanding.
Core principle: Don't just know what to do - understand why and how.
Trigger: After session-resume for Fresh Start sessions, or manual deep restore
Read and parse the status file:
# See what's changed
git status
# Review recent commits for context
git log --oneline -10
# See uncommitted changes
git diff --stat
Based on focus area, read relevant files:
If working on feature:
If debugging:
If refactoring:
# Run tests to verify state
npm test
# Check for lint errors
npm run lint
# Verify build passes
npm run build
Construct understanding:
## Current Context
### What We're Building
[Feature description from STATUS.json focus area]
### Where We Are
- Branch: [branch name]
- Last commit: [commit message]
- Uncommitted: [files and their purpose]
### Key Files
- `path/to/main.ts` - [what it does, current state]
- `path/to/test.ts` - [test coverage status]
### Decisions Made
- [Decision 1 from keyDecisions]
- [Decision 2]
### What's Next
1. [nextAction from STATUS.json]
2. [Logical following step]
### Potential Issues
- [Any warnings from tests/lint]
- [Any blockers noted]
Present restored context and options:
Context fully restored. Here's where we are:
[Mental model summary]
Ready to continue. Options:
1. Proceed with: [next action]
2. Review specific file first
3. Run full test suite
4. See detailed task breakdown
What would you like to do?
For complex projects or long breaks:
๐ Full Context Restore
Loading STATUS.json...
โ Project: my-app
โ Branch: feature/user-auth
โ Focus: Authentication system
Reviewing git state...
โ Last commit: a7f3c2e - feat: add login form
โ 2 uncommitted files:
- src/auth/reset.ts (new)
- src/auth/reset.test.ts (new)
Reading key files...
โ src/auth/login.ts - Login form complete
โ src/auth/reset.ts - Password reset in progress (50%)
โ Tests: 45 passing, 0 failing
Mental Model:
- Building password reset flow
- Login and validation complete
- Reset flow needs: email template, token generation
- Using nodemailer (decided last session)
Next action: Add forgot password email template
Ready to continue?
Use context-restore when:
Skip context-restore when:
Pairs with:
Calls: