# can you find a skill or slash command which tells you or claude to go over my past conversation a... ## Retrieval Notes - Session id: `019d2014-9922-7a61-baa4-6b276f76bfe1` - Source: `Agent Client fallback` - Last activity: `2026-03-24T15:21:47.700Z` ## My Notes <!-- Add your notes here. This section is preserved across syncs. --> ## Conversation ### User can you find a skill or slash command which tells you or claude to go over my past conversation and finding things happen a lot and might be solved by a permant skillm, or claude.md etc. ### Assistant I’m checking the available skills for one that explicitly turns repeated conversation patterns into durable system changes, then I’ll point you to the closest slash-command-style workflow if there is one. ### Assistant I found the closest built-in mechanism. I’m checking whether there’s also a dedicated Claude slash command, or whether this is skill-only right now. ### Assistant There is also a stronger match for the “happens a lot across past conversations” part. I’m reading that command now, since `evolve` is session-local and may not be the best fit for pattern-finding across history. ### User it's not evolve. thats clearly not what idescribed ### Assistant `/friction-analysis` is the one you described. It’s a Claude command at [evolve.md](/Users/nickyoung/.claude/commands/friction-analysis.md), and its purpose is to scan recent sessions for repeated friction, classify the root cause, and suggest the right permanent fix layer: `CLAUDE.md`, knowledge, commands, skills, hooks, scripts, or architecture. The key distinction is: - `/evolve` = capture a lesson from the current session - `/friction-analysis` = look across past conversations for recurring patterns and propose system fixes You’d use it like: ```text /friction-analysis 7 ``` That means “analyze the last 7 days.” If you want, I can also find whether there’s a Codex-native equivalent yet, or make one.