← ClaudeAtlas

reflectlisted

Use Recall Reflect to review AI coding workflow history as a conversation-first timeline and discuss observed patterns before changing behavior. Trigger when the user asks to reflect on a project, review AI coding workflow, inspect workflow friction, discuss repeated corrections, review handoffs, or explore possible calibration.
samzong/Recall · ★ 109 · AI & Automation · score 83
Install: claude install-skill samzong/Recall
# Reflect ## Overview Reflect is the official `recall-reflect` Recall extension. It is a discussion-first workflow for reviewing AI coding sessions through Recall's stable CLI JSON and JSONL protocol. The extension reconstructs a conversation-first timeline across sessions and surfaces observed patterns as questions for the user, not as automatic conclusions or edits. Use this skill when the user wants project-level reflection on AI coding process, workflow friction, handoffs, repeated corrections, scope drift, or possible future calibration. Reflect output is evidence for discussion, not permission to change skills, prompts, configs, instruction files, or project files. ## Core Rule Do not treat an observed pattern as a calibration target, workflow change, or proposal unless the user explicitly confirms the interpretation. Ask first, then act only on confirmed direction. ## Scope Defaults Scope to the current repo unless the user asks otherwise. Resolve the project directory with: ```bash git rev-parse --show-toplevel ``` Run Reflect with structured output. Prefer user-facing dispatch when the extension is installed and managed by Recall: ```bash recall reflect --project /absolute/project/path --format json ``` Direct extension invocation is also acceptable when testing or calling the extension binary explicitly: ```bash recall-reflect --project /absolute/project/path --format json ``` Add `--time 30d` or `--source <source>` when the user narrows the review. Us