scan-project

Scan a project workspace and generate a .memory/ directory with SUMMARY.md and STATUS.md.

6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/candradesm/zsh-config --skill scan-project-candradesm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scan-project
Source: https://github.com/candradesm/zsh-config/tree/main/.config/opencode/skills/scan-project
Command: npx skills add https://github.com/candradesm/zsh-config --skill scan-project-candradesm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps you quickly get oriented when joining a new codebase by scanning the local workspace to infer project structure, technology stack, and existing documentation, and by initializing a persistent memory store for future sessions.

Core Features & Use Cases

  • Scan project layout to map top-level directories and common files (build files, source, docs).
  • Detect tech stack by listing languages, build tools, and configuration files.
  • Generate memory bank in .memory/ with STATUS.md and SUMMARY.md for quick reference.

Quick Start

Run scan-project at the start of a project to initialize the memory bank and capture workspace context.

Frequently Asked Questions about scan-project

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

FAQPage Schema
How do I build a memory bank for a new project workspace?

Build a memory bank by scanning the unfamiliar workspace to infer project structure, technology stack, and existing documentation. This initializes a .memory/ directory containing SUMMARY.md and STATUS.md for future reference.

What is the best way to document an unfamiliar tech stack during onboarding?

Document an unfamiliar tech stack by scanning the local workspace to list languages, build tools, and configuration files. This generates a structured summary within a persistent memory store for quick reference.

Can I use workspace analysis to restore a stale or missing project context?

Yes, workspace analysis restores stale or missing project context. It applies when returning after a long break by scanning the layout and refreshing the persistent memory store with updated directory and file mappings.

Does project onboarding require any dependencies to map top-level directories?

No, project onboarding to map top-level directories requires no dependencies. The scan runs directly on the local workspace to detect build files, source code, and documentation without needing external tools.

What limitations exist when scanning a local workspace for existing documentation?

A limitation when scanning a local workspace for existing documentation is that the tool infers structure from common files and top-level directories, meaning deeply nested or non-standard configurations might be missed.