/summarize-session
Summarize the current session and generate reusable Claude rules, skills, or commands.
$ npx -y skills add lbb00/ai-rules-sync --skill summarize-session --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/summarize-session
Context preview
The summary Claude sees to decide when to auto-load this skill.
Summarize the current session and generate reusable Claude rules, skills, or commands.
SKILL.md
summarize-session.SKILL.mdname: summarize-session
description: Summarize the current session and generate reusable Claude rules, skills, or commands.
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**
- What problems were solved?
- What code was written or modified?
- What workflows were performed?
- What decisions were made and why?
2. **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
3. **Generate Artifacts**
For each identified pattern, create the appropriate artifact:
**Rules** → `.claude/rules/<name>/RULE.md`
---
name: rule-name
description: Brief description
---
# Rule Name
## When to Apply
...
## Guidelines
...
**Skills** → `.claude/skills/<name>/SKILL.md`
---
name: skill-name
description: Brief description
---
# Skill Name
## Instructions
1. Step 1
2. Step 2
...
**Commands** → `.claude/commands/<name>.md`
# Command Name
Description of what this command does.
## Steps
1. ...
2. ...
4. **Validate Artifacts**
- Ensure artifacts are general enough to be reusable
- Remove session-specific details
- Test that instructions are complete and actionable
5. **Document Session Summary**
- What was accomplished
- What artifacts were generated
- 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`
Read more
name: summarize-session description: Summarize the current session and generate reusable Claude rules, skills, or commands.
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**
- What problems were solved?
- What code was written or modified?
- What workflows were performed?
- What decisions were made and why?
2. **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
3. **Generate Artifacts**
For each identified pattern, create the appropriate artifact:
**Rules** → `.claude/rules/<name>/RULE.md`
--- name: rule-name description: Brief description --- # Rule Name ## When to Apply ... ## Guidelines ...
**Skills** → `.claude/skills/<name>/SKILL.md`
--- name: skill-name description: Brief description --- # Skill Name ## Instructions 1. Step 1 2. Step 2 ...
**Commands** → `.claude/commands/<name>.md`
# Command Name Description of what this command does. ## Steps 1. ... 2. ...
4. **Validate Artifacts**
- Ensure artifacts are general enough to be reusable
- Remove session-specific details
- Test that instructions are complete and actionable
5. **Document Session Summary**
- What was accomplished
- What artifacts were generated
- 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`
English · 中文 · Documentation AI Rules Sync (AIS) — Install, compose, update, and publish native agent assets from multiple Git repositories across all your projects. AIS is an asset federation toolkit, not a format converter.
Repo: lbb00/ai-rules-sync
Other skills on ai-rules-sync.
sync-readme
Synchronize English README.md with Chinese README_ZH.md, maintaining content parity.
update-knowledge-base
Analyze code changes and update KNOWLEDGE_BASE.md with architectural and feature changes.

