Reflect FAQs

Question 1

When should I use this skill?

Accepted Answer

Use Reflect when you need to catch up on a project ('where were we?'), perform a project retrospective, document decisions for your CLAUDE.md file, or identify knowledge gaps that you should study to improve your technical skills.

Question 2

Can Reflect analyze activity across multiple projects?

Accepted Answer

Yes. While it excels at deep-dives into specific projects using git integration, it also supports a 'cross-project' mode. This allows you to look back at your activity over a specific calendar timeframe (like the last two weeks) across all your Claude Code workspaces.

Question 3

What does the Reflect skill do?

Accepted Answer

The Reflect skill analyzes your past interactions with Claude and your git commit history to extract actionable insights. It identifies learning patterns, surfaces architectural decisions, highlights recurring mistakes (antipatterns), and helps you resume work on older projects by summarizing previous progress.

Question 4

What are the analytical 'lenses' in Reflect?

Accepted Answer

Reflect uses specialized lenses to tailor its analysis. These include 'where-were-we' for context, 'learning' for growth tracking, 'gaps' for identifying weaknesses, 'mentor' for process review, 'retro' for project conclusions, and 'decisions' for architectural documentation.

Question 5

How does Reflect improve my developer workflow?

Accepted Answer

It automates context restoration and self-reflection. Instead of manually scrolling through old chats, Reflect uses iterative semantic search and structured extraction to give you a high-level view of your development process, helping you learn faster and maintain better documentation.

Reflect

Reflect

主要功能

使用场景

主要功能

使用场景