القائمة
Display Claude conversation history in an easy-to-scan format showing recent sessions with dates, projects, and topics. Use when you want to review past conversations or resume a previous session.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | history |
| description | Display Claude conversation history in an easy-to-scan format showing recent sessions with dates, projects, and topics. Use when you want to review past conversations or resume a previous session. |
| disable-model-invocation | true |
Please read my global conversation history from C:/Users/carsten.jorgensen/.claude/history.jsonl and present it in an easy-to-scan format.
For each conversation, show:
IMPORTANT: Format as a plain text table with properly padded columns (NOT markdown tables).
Focus on the most recent 10 conversations in the first table. If there are more, show another 5-7 in an "Additional Recent Conversations" table.
💡 Tip: Resume any conversation by running:
Manage git worktrees using the gwm script. Supports creating, listing, removing, and checking status of worktrees. Use when the user says "create git worktree", "new worktree", or needs to work with multiple branches simultaneously via git worktrees.
Update the project's CLAUDE.md with meta learnings, conventions, gotchas, and significant codebase changes. Use when the user asks to update CLAUDE.md, capture learnings, document project conventions, or reflect recent work in the project guide.
Review the current Pull Request that has been checked out locally with structured feedback on code quality, issues, testing, and suggestions. Use when you need a comprehensive code review of a PR branch.
Catch up on branch changes by reviewing all changes between current branch and master/main, analyzing key files, and providing a comprehensive summary. Use when you need to understand what changed in a feature branch.
Perform a refactor pass focused on simplicity after recent changes. Use when the user asks for a refactor/cleanup pass, simplification, or dead-code removal and expects build to verify behavior.
Analyze the specified function from the given file with detailed line-by-line breakdown. Use when you need to understand what a function does, how it works, and why it was implemented that way.
