agentleFS
NoaiRoxNoaiRox/specialist-agent/skills/recall/SKILL.md

recall

Skill2 starsChanged 9 months agoMITView on GitHub

Use when you need to retrieve a past decision, preference, or convention that was saved with /remember.

142 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use addskill, apply-firmware and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ryanportfolioSkill

    addskill

    Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.

    Also in 6 projects that use this

  • ryanportfolioSkill

    apply-firmware

    Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.

    Also in 6 projects that use this

  • +10 more from ryanportfolio

The file

Files
SKILL.md

/recall - Query Session Memory

Recall decisions, preferences, and lessons from previous sessions.

Query: $ARGUMENTS

Workflow

Step 1: Load Memory

const memoryFile = '.claude/session-memory.json';

if (!exists(memoryFile)) {
  return "No session memory found. Use /remember to save memories.";
}

const memory = JSON.parse(read(memoryFile));

Step 2: Process Query

If "all" or empty:

Show full memory summary.

If specific topic:

Search in:

  1. decisions[].topic
  2. preferences keys
  3. patterns.avoided
  4. patterns.preferred
  5. lessons[].issue

Step 3: Format Output

Output Formats

Full Memory (/recall all)

══════════════════════════════════════════════
           📝 PROJECT MEMORY
══════════════════════════════════════════════

Project: [name]
Last updated: [date]

──────────────────────────────────────────────
           DECISIONS (N)
──────────────────────────────────────────────

• [Topic]: [Decision]
  Reason: [Why]
  Date: [When]

• [Topic]: [Decision]
  Reason: [Why]
  Date: [When]

──────────────────────────────────────────────
           PREFERENCES
──────────────────────────────────────────────

Code Style:
  • Quotes: [value]
  • Indent: [value]
  • Semicolons: [value]

Naming:
  • Components: [convention]
  • Files: [convention]

──────────────────────────────────────────────
           PATTERNS
──────────────────────────────────────────────

✓ Preferred:
  • [pattern]
  • [pattern]

✗ Avoided:
  • [pattern]
  • [pattern]

──────────────────────────────────────────────
           LESSONS LEARNED (N)
──────────────────────────────────────────────

• Issue: [what happened]
  Solution: [how to fix]
  Prevention: [rule]

══════════════════════════════════════════════

Specific Topic (/recall state management)

──── /recall: state management ────

Found 2 related memories:

📌 Decision: State Management
   Use Zustand instead of Redux
   Reason: Simpler API, less boilerplate
   Decided: 2024-01-15

📌 Pattern (Avoid): Redux
   We avoid Redux in this project

Related:
  • See also: "React Query" decision

No Results

──── /recall: [topic] ────

No memories found for "[topic]".

Suggestions:
  • Try /recall all to see all memories
  • Use /remember to add new memories

Query Examples

/recall                    # Show recent memories
/recall all                # Show all memories
/recall state management   # Search for topic
/recall testing           # Search for topic
/recall decisions         # Show only decisions
/recall preferences       # Show only preferences
/recall patterns          # Show patterns
/recall lessons           # Show lessons learned

Rules

  1. Fuzzy match - "state" matches "State Management"
  2. Show context - Include reason and date
  3. Suggest related - Link to similar memories
  4. Handle empty - Graceful message if no memory

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.