ctx-recall
Browse session history. Use when referencing past discussions or finding context from previous work.
Best use case
ctx-recall is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Browse session history. Use when referencing past discussions or finding context from previous work.
Teams using ctx-recall should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/ctx-recall/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How ctx-recall Compares
| Feature / Agent | ctx-recall | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Browse session history. Use when referencing past discussions or finding context from previous work.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Browse, inspect, and import AI session history. ## When to Use - When the user asks "what did we do last time?" - When looking for context from previous work sessions - When importing sessions to the journal for enrichment - When searching for a specific session by topic or date ## When NOT to Use - When the user just wants current context (use `ctx-status` or `ctx-agent` instead) - For modifying session content (browsing is read-only) ## Subcommands ### `ctx journal source` ```bash ctx journal source --limit 5 ``` ### `ctx journal source --show` / `--latest` ```bash ctx journal source --show <slug-or-id> ctx journal source --latest ``` ### `ctx journal import` ```bash ctx journal import --all # Import new sessions only ctx journal import --all --regenerate # Re-import all ``` ## Typical Workflows **"What did we work on recently?"** ```bash ctx journal source --limit 5 ``` **"Import everything to the journal"** ```bash ctx journal import --all ``` Then suggest `ctx-journal-enrich-all` for enrichment. ## Quality Checklist - [ ] Used the right subcommand for user intent - [ ] Applied filters if user mentioned project, date, or topic - [ ] For import, mentioned the normalize/enrich pipeline
Related Skills
ctx-verify
Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.
ctx-skill-creator
Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.
ctx-sanitize-permissions
Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.
ctx-prompt
Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.
ctx-journal-normalize
Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.
ctx-import-plans
Import plan files into project specs directory. Use to convert external plans into project-tracked specs.
ctx-compact
Archive completed tasks and trim context. Use when context files are growing large.
ctx-check-links
Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.
ctx-add-task
Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.
ctx-add-learning
Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.
ctx-add-decision
Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.
ctx-add-convention
Record a coding convention. Use when a repeated pattern should be codified so all sessions follow it consistently.