Using gitglimpse with Claude Code

The /standup slash command

Claude Code supports custom slash commands that live in your repository. gitglimpse ships a one-line init command that creates the right files in .claude/commands/ so you can type /standup inside Claude Code and get a polished daily summary. It also generates /report, /week, and /pr commands for weekly summaries, custom date ranges, and pull request descriptions. Because the command files are committed to the repo, every teammate who clones it gets the slash commands automatically — zero per-user setup.

Three-command setup

Run these commands from your project root to install the slash commands and start using them immediately:

# 1. Generate the .claude/commands/ files (standup, report, week, pr)
glimpse init

# 2. Commit so teammates get it too
git add .claude/commands/ && git commit -m "add gitglimpse slash commands"

# 3. Use it inside Claude Code
/standup

glimpse init --cursor generates the same command files for Cursor.

JSON mode is the glue

Under the hood, the slash command runs glimpse standup --json. This outputs structured data — an array of tasks with descriptions, effort estimates, and file lists — that Claude Code can parse and reason over. Claude then rewrites the raw data into natural language, groups related commits, and formats everything for Slack or your team's standup doc. You get the accuracy of git history with the readability of a human-written update.

Why this matters

• •No copy-pasting terminal output — Claude Code reads the JSON and writes the summary inline.
• •Customizable tone — ask Claude to be concise, detailed, or formatted for a specific Slack channel.
• •Works with any repo — the slash command reads the local git log, so it works on monorepos, forks, and private projects alike.
• •Works with Claude Code and Cursor — same commands, same workflow.