summarize-session

Summarize Session

Purpose

At the end of a productive coding session, analyze the conversation to extract reusable patterns and generate Claude Code artifacts (rules, skills, commands) that can accelerate future work.

Instructions

1. Review Session Activity
2. What problems were solved?
3. What code was written or modified?
4. What workflows were performed?
5. What decisions were made and why?

1. Identify Patterns

Rules Candidates (coding standards, project conventions):

• Repeated code style corrections
• Error patterns that were fixed
• Best practices established
• Project-specific conventions

Skills Candidates (multi-step workflows):

• Complex operations performed multiple times
• Sequences of commands that go together
• Integration or deployment workflows
• Testing or validation procedures

Commands Candidates (single-action shortcuts):

• Frequently used command combinations
• Build/test/deploy shortcuts
• Common git operations
• Project-specific utilities

1. Generate Artifacts

For each identified pattern, create the appropriate artifact:

Rules → .claude/rules/<name>/RULE.md ```markdown

name: rule-name description: Brief description

# Rule Name

## When to Apply ...

## Guidelines ... ```

Skills → .claude/skills/<name>/SKILL.md ```markdown

name: skill-name description: Brief description

# Skill Name

## Instructions

1. Step 1
2. Step 2

... ```

Commands → .claude/commands/<name>.md ```markdown # Command Name

Description of what this command does.

## Steps

1. ...
2. ...

```

1. Validate Artifacts
2. Ensure artifacts are general enough to be reusable
3. Remove session-specific details
4. Test that instructions are complete and actionable

1. Document Session Summary
2. What was accomplished
3. What artifacts were generated
4. Recommendations for next session

Output Format

## Session Summary

### Accomplished
- [List of completed tasks]

### Generated Artifacts

#### Rules
- `<rule-name>`: <description>

#### Skills
- `<skill-name>`: <description>

#### Commands
- `<command-name>`: <description>

### Next Steps
- [Recommendations for future work]

Examples

Example: After Adding a New Adapter

Identified Pattern: Multi-step process for adding adapters Generated: Skill new-adapter

Example: After Fixing Multiple Type Errors

Identified Pattern: TypeScript strict mode conventions Generated: Rule typescript-conventions

Example: After Repeated Test Commands

Identified Pattern: Test-then-commit workflow Generated: Command test-and-commit