Feature Request
Problem
When reviewing code, the /ce-code-review command provides general analysis, but users cannot easily see who last modified each line and why — the core context that git blame provides. To get this, users must switch to a terminal and manually run git blame, breaking the workflow flow.
Proposed Solution
Add a /ce:git blame subcommand (or --blame flag on /ce-code-review) that fetches per-line blame information and displays it inline during code review, e.g.:
/ce:git blame src/utils/auth.ts
This would show commit hash, author, and date for each modified line alongside the review commentary, helping reviewers understand change context without leaving Claude Code.
Use Case
A developer reviewing a security-sensitive file wants to know which commit introduced a given pattern and who authored it — without switching context to a terminal.
Alternatives Considered
Users currently run git blame in a separate terminal, but this breaks the conversational review flow and requires leaving the Claude Code session.
Feature Request
Problem
When reviewing code, the
/ce-code-reviewcommand provides general analysis, but users cannot easily see who last modified each line and why — the core context thatgit blameprovides. To get this, users must switch to a terminal and manually run git blame, breaking the workflow flow.Proposed Solution
Add a
/ce:git blamesubcommand (or--blameflag on/ce-code-review) that fetches per-line blame information and displays it inline during code review, e.g.:This would show commit hash, author, and date for each modified line alongside the review commentary, helping reviewers understand change context without leaving Claude Code.
Use Case
A developer reviewing a security-sensitive file wants to know which commit introduced a given pattern and who authored it — without switching context to a terminal.
Alternatives Considered
Users currently run
git blamein a separate terminal, but this breaks the conversational review flow and requires leaving the Claude Code session.