Slash Command

/reflect

From eng

Review session and capture learnings for future sessions

Install

npx claudepluginhub postsharp/postsharp.engineering.aiskills --plugin eng

Prompt Preview

# Self-Improvement and Reflection

Review the current session and identify learnings that should be captured for future sessions.

## Instructions

1. **Review the session**: Look back at the conversation and identify:
   - Mistakes made and how they were resolved
   - Patterns that worked well
   - Knowledge gaps that caused inefficiency
   - User corrections or feedback

2. **Categorize learnings**:
   - **Critical rules**: Things that must always/never be done
   - **Patterns**: Reusable approaches for common tasks
   - **Domain knowledge**: Codebase-specific information
   - **Debugging...

Command Content

Other plugins with /reflect

/reflect

sc/

Analyzes and validates task adherence, session progress, and completion using Serena MCP reflection tools. Provides recommendations and updates session metadata. Supports --type and analysis flags.

claude-scholar

3.4k

/reflect

Scans session history for corrections, extracts learnings, and updates CLAUDE.md files across project, global, and subdirectory tiers with human review. Supports dry-run, dedupe, organize, and scan flags.

ReadEditWrite+5

claude-reflect

822

/reflect

Analyzes filtered diary entries for patterns in user preferences, code decisions, solutions, and challenges, then synthesizes insights and proposes CLAUDE.md updates.

claude-memory

288

/reflect

Analyzes current session, detects context, extracts summary and insights via subagents, guides selection, and integrates into User/Project memory.

reflexion

/reflect

Analyzes chat history, Claude instructions, commands, and config to suggest interactive improvements and implements approved changes, producing updated instructions.

swift-engineering

/reflect

Guides reflection on recent work like bug fixes or features to extract root causes, patterns, decisions. Records learnings via tk learn and tk decide.

tasuku

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitDec 12, 2025

Actions

View Source View Plugin View on GitHub View README

# Self-Improvement and Reflection Review the current session and identify learnings that should be captured for future sessions. ## Instructions 1. **Review the session**: Look back at the conversation and identify: - Mistakes made and how they were resolved - Patterns that worked well - Knowledge gaps that caused inefficiency - User corrections or feedback 2. **Categorize learnings**: - **Critical rules**: Things that must always/never be done - **Patterns**: Reusable approaches for common tasks - **Domain knowledge**: Codebase-specific information - **Debugging...

Self-Improvement and Reflection

Review the current session and identify learnings that should be captured for future sessions.

Instructions

Review the session: Look back at the conversation and identify:

Mistakes made and how they were resolved
Patterns that worked well
Knowledge gaps that caused inefficiency
User corrections or feedback

Categorize learnings:

Critical rules: Things that must always/never be done
Patterns: Reusable approaches for common tasks
Domain knowledge: Codebase-specific information
Debugging techniques: How to diagnose specific issues

Update documentation:

Add critical rules to CLAUDE.md under appropriate sections
Add domain-specific learnings to relevant CLAUDE.md files in subdirectories
Keep entries concise and actionable

Consider scope - where should the improvement go?

Repo-specific (CLAUDE.md in the repo):

Codebase structure and architecture
Project-specific patterns and conventions
Build quirks for this specific repo
Domain knowledge about the code

Directory-specific (CLAUDE.md in subdirectory):

Context-specific patterns (e.g., Standalone/CLAUDE.md for standalone test patterns)
Component-specific rules

AI Skills repo (PostSharp.Engineering.AISkills):

General devops and git workflow knowledge
How the team works (PR process, release workflow)
Cross-repo conventions and patterns
Build system (Build.ps1) improvements
GitHub/TeamCity API patterns

Format:

Use bullet points or numbered lists
Include concrete examples where helpful
Avoid verbose explanations - future Claude instances should quickly scan and apply

Output

Summarize:

What learnings were added

Where they were added

Why they're valuable for future sessions

Self-Improvement and Reflection

Review the current session and identify learnings that should be captured for future sessions.

Instructions

Review the session: Look back at the conversation and identify:
- Mistakes made and how they were resolved
- Patterns that worked well
- Knowledge gaps that caused inefficiency
- User corrections or feedback
Categorize learnings:
- Critical rules: Things that must always/never be done
- Patterns: Reusable approaches for common tasks
- Domain knowledge: Codebase-specific information
- Debugging techniques: How to diagnose specific issues
Update documentation:
- Add critical rules to CLAUDE.md under appropriate sections
- Add domain-specific learnings to relevant CLAUDE.md files in subdirectories
- Keep entries concise and actionable
Consider scope - where should the improvement go?

Repo-specific (CLAUDE.md in the repo):
- Codebase structure and architecture
- Project-specific patterns and conventions
- Build quirks for this specific repo
- Domain knowledge about the code
Directory-specific (CLAUDE.md in subdirectory):
- Context-specific patterns (e.g., Standalone/CLAUDE.md for standalone test patterns)
- Component-specific rules
AI Skills repo (PostSharp.Engineering.AISkills):
- General devops and git workflow knowledge
- How the team works (PR process, release workflow)
- Cross-repo conventions and patterns
- Build system (Build.ps1) improvements
- GitHub/TeamCity API patterns
Format:
- Use bullet points or numbered lists
- Include concrete examples where helpful
- Avoid verbose explanations - future Claude instances should quickly scan and apply

Output

Summarize:

What learnings were added
Where they were added
Why they're valuable for future sessions