smart-explore

Explore codebases using stored session memory to prioritize targeted file reads.

8|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill smart-explore-msapps-mobile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-explore
Source: https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/cowork-mem/skills/smart-explore
Command: npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill smart-explore-msapps-mobile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Many project explorations read every file from scratch and miss prior session context, wasting time and duplicating work. smart-explore uses previously recorded memory to prioritize where to look, surface past decisions, and quickly build an accurate mental model of a codebase.

Core Features & Use Cases

  • Memory-first discovery: Query vectorized memory for architecture notes, recent decisions, and known issues before opening files.
  • Targeted file reads: Use memory signals to select the most relevant files to inspect instead of scanning the entire repository.
  • Summarization and insight capture: Produce a concise project overview (purpose, current state, key files, blockers, next steps) and persist new findings back into memory.
  • Use cases: developer onboarding, resuming paused work, auditing code ownership or recent changes, and orienting at the start of new sessions on ongoing projects.

Quick Start

Run a memory-guided exploration that checks previous session notes for architecture and recent edits, reads the most relevant files, summarizes the project's purpose and current state, and saves any new insights to memory.

Frequently Asked Questions about smart-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explore a codebase using previous session memory instead of scanning every file?

Memory-guided codebase exploration uses a vectorized memory index to query past architecture notes and recent decisions, prioritizing targeted file reads over blind scanning to quickly build an accurate project mental model. It surfaces prior context to avoid duplicating work.

What is the best way to onboard developers onto an existing project with prior session history?

Developer onboarding via memory-guided exploration retrieves timeline data of recent edits and past decisions, selectively reads relevant files, generates a project overview summarizing purpose and current state, and saves new insights back to memory.

Can I resume paused work on a codebase by retrieving prior decisions and file history?

Resuming paused work leverages stored session memory to retrieve prior decisions and recent file history, enabling targeted context-building that skips redundant file scanning and immediately surfaces known issues and next steps.

Does project exploration require a vectorized memory index to function?

Project exploration requires a vectorized memory index for querying past architecture notes, alongside tools for timeline retrieval of recent edits, file reading capabilities, and functionality to persist new findings back into memory.

How does memory-guided codebase auditing handle context-building and insight capture?

Memory-guided codebase auditing handles context-building by querying vectorized memory for past decisions, performing targeted file reads, and capturing insights by producing a concise project overview that is persisted back into memory for future sessions.