reflect
Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
Best use case
reflect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
Teams using reflect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/reflect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How reflect Compares
| Feature / Agent | reflect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reflect on the conversation and update the brain. Use when wrapping up, after mistakes or corrections, or when significant codebase knowledge was gained. Triggers: "reflect", "remember this".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Reflect Review the conversation and persist learnings — to `brain/`, to skill files, or as structural enforcement. ## Process 1. **Read `brain/index.md`** to understand what notes already exist 2. **Scan the conversation** for: - Mistakes made and corrections received - User preferences and workflow patterns - Codebase knowledge gained (architecture, gotchas, patterns) - Tool/library quirks discovered - Decisions made and their rationale - Friction in skill execution, orchestration, or delegation - Repeated manual steps that could be automated or encoded 3. **Skip** anything trivial or already captured in existing brain files 4. **Route each learning** to the right destination (see Routing below) 5. **Update `brain/index.md`** if any brain files were added or removed ## Routing Not everything belongs in the brain. Route each learning to where it will have the most impact. ### Structural enforcement check Before routing a learning to `brain/`, ask: can this be a lint rule, script, metadata flag, or runtime check? If yes, encode it structurally and skip the brain note. See `brain/principles/encode-lessons-in-structure.md`. ### Brain files (`brain/`) Codebase knowledge, principles, gotchas — anything that informs future sessions. This is the default destination. Use the `brain` skill for writing conventions. - One topic per file. File name = topic slug. - Group in directories with index files using `[[wikilinks]]`. - No inlined content in index files. ### Skill improvements (`.agents/skills/<skill>/`) If a learning is about how a specific skill works — its process, prompts, or edge cases — update the skill directly. ### Backlog items Follow-up work that can't be done during reflection — bugs, non-trivial rewrites, tooling gaps. File as a todo or backlog item. ## Summary ``` ## Reflect Summary - Brain: [files created/updated, one-line each] - Skills: [skill files modified, one-line each] - Structural: [rules/scripts/checks added] - Todos: [follow-up items filed] ```
Related Skills
ruminate
Mine past Claude Code conversations for uncaptured patterns, corrections, and knowledge. Cross-references with existing brain content. Triggers: "ruminate", "mine my history".
review
Principle-grounded review of code changes, PRs, or plans. Use when asked to review, critique, or assess quality of work — "review", "review this", "code review", "check this".
plan
Break down medium-to-large tasks into phased plans in brain/plans/. Planning only — does not implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
meditate
Audit and evolve the brain vault — prune outdated content, discover cross-cutting principles, review skills for structural encoding opportunities. Triggers: "meditate", "audit the brain".
brain
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers: brain/ modifications, "add to brain".
self-reflection
Continuous self-improvement through structured reflection and memory
openclaw-reflect
Self-improvement layer with evaluation separation, rollback, and tiered operator gates. Observes outcomes across sessions, detects recurring patterns, proposes improvements, validates proposals through a separate evaluator invocation, and applies changes safely with snapshot/rollback capability.
claude-reflect
Execute self-learning system that captures corrections during sessions and syncs them to CLAUDE.md. Use when discussing learnings, corrections, or when the user mentions remembering something. Trigger with phrases like "remember this", "don't forget", "use X not Y", or "actually...".
self-reflection
Continuous self-improvement through structured reflection and memory
Self-Improving Agent (Proactive Self-Reflection)
Self-reflection + Self-criticism + Self-learning + Self-organizing memory. Agent evaluates its own work, catches mistakes, and improves permanently. Use before starting work and after responding to the user.
reflect
Learning capture system that extracts HIGH/MED/LOW confidence patterns from conversations to prevent repeating mistakes. Use after user corrections ("no", "wrong"), praise ("perfect", "exactly"), or when discovering edge cases. Complements .squad/agents/{agent}/history.md and .squad/decisions.md.
commit-with-reflection
Git提交与调试反思报告生成技能。自动分析开发过程中的错误、调试步骤和解决方案,生成结构化的中文反思报告,并创建包含报告引用的Git提交。触发词:反思提交、智能提交、生成调试报告、commit with reflection。