Skip to content
This repository was archived by the owner on Sep 23, 2025. It is now read-only.

Consider renaming 'reviews' to 'walkthroughs' #14

@nikomatsakis

Description

@nikomatsakis

Consider Renaming 'Reviews' to 'Walkthroughs'

Problem

The term "review" may bring the wrong connotations - it suggests the AI is evaluating or critiquing the user's code, when the actual purpose is more collaborative and educational.

Proposed Change

Rename "reviews" to "walkthroughs" throughout the system to better reflect the intended purpose:

  • Guided tour: AI explains what the code does and why
  • Educational: Helps users understand the changes
  • Collaborative: AI is helping, not judging
  • Exploratory: Invites questions and deeper investigation

Impact Areas

  • MCP tool name: present_walkthrough instead of present_review
  • UI labels and panel titles
  • Documentation and user guide
  • AI guidance and prompts
  • User mental model of the feature

Benefits

  • Clearer communication of the feature's collaborative nature
  • Reduces potential user anxiety about being "reviewed"
  • Better aligns terminology with actual use case
  • More inviting for users to engage with the feature

Context

This came up during discussion of the overall user experience and how terminology affects user perception of AI assistance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions