/rewind-summary

The user is about to rewind the conversation to: "$ARGUMENTS"

Create a brief summary (5-10 lines max) of what was accomplished AFTER that point:

Required sections:

1. What was fixed/completed (1-2 lines)
2. Key changes (files, methods, bugs fixed)
3. Important findings or discoveries
4. Commit info (if any)
5. Test results (pass/fail counts)

Format:

• Use markdown
• Be concise and actionable
• End with a transition to next task. Examples:
  • "Fixed authentication bug. Now let's add rate limiting."
  • "Implemented user service. Ready to wire up the API endpoints."
  • "Explored codebase and found N+1 queries. Let's optimize them."
  • "Refactored payment logic. Now add webhook handlers."
  • "Investigated database performance. Need schema access to proceed."

Skip:

• Verbose explanations
• Step-by-step details
• Code snippets
• Full file paths (use relative paths only)