Cursor Blame
This skill helps you investigate the history and intent behind code changes made with AI assistance.
When to Use
- When asking about why code was written a certain way
- When investigating the history of a file or function
- When understanding what alternatives were considered
- When tracing the evolution of a codebase
How It Works
Cursor Blame correlates code with the AI conversations that produced it, providing:
- Conversation context and summaries
- Decision rationale and tradeoffs discussed
- Models used during development
- Timeline of changes
Usage
Simply ask questions like:
- "Why was this function implemented this way?"
- "What was the reasoning behind this architecture decision?"
- "Show me the history of changes to this file"