25 Things to Ask Claude Code on Your Commute (Voice Commands That Actually Work)

TL;DR: A lot of engineering work is just asking questions: Is CI green? What's waiting on me? What did the team say? With Claude Code on voice, your commute can cover that part. Below are 25 things to ask Claude Code while you drive, grouped by job, with what actually happens for each one, plus how to phrase requests so they work well by voice. Everything here works with carcode, the open-source Siri bridge for Claude Code, and needs nothing beyond tools Claude Code already uses: gh, git, your repos and the connectors you've set up.

How This Works

You say "Hey Siri, Jarvis". Your words go to Claude Code on your Mac, which works in your repos folder with your GitHub login and connectors, and the answer is spoken back through CarPlay, your AirPods or the phone speaker. If you haven't set it up yet, How to Run Claude Code With Siri takes about five minutes.

Two rules shape everything below:

• Answers come back short and spoken. Claude Code is told to answer in one or two sentences, with no code read aloud. Anything long waits for your screen.
• It asks before it acts for you. Sending, merging, approving, posting and deleting are all read back first and need a spoken "confirm". Code changes land as draft pull requests, never on main.

Catch Up on Pull Requests

1. "Any pull requests waiting on me?"

Lists PRs where you're a requested reviewer, using the GitHub CLI.

2. "What's the status of my open PRs?"

For each of your PRs: CI state, approvals and whether there are unresolved comments.

3. "Summarize PR forty-two."

Reads the description and the diff, then tells you what it changes and anything that looks risky. Say numbers as words; dictation handles "forty-two" better than "four two".

4. "What did reviewers say on my latest PR?"

Reads the review comments and tells you what's being asked.

5. "Approve PR forty-two." → "Confirm."

Reads the action back ("Approve PR forty-two on the website repo?") and only approves after you confirm. Save this for small, low-risk PRs you've already looked at.

Check CI and Builds

6. "Is CI green on the website repo?"

Checks the latest workflow runs on the default branch.

7. "Why did the last build fail?"

Reads the failed job's logs and tells you the failing step and the likely cause.

8. "Run the tests on the API repo."

A test run usually takes longer than Siri will wait, so you'll hear "One moment". The job keeps running in the background; ask "Status" any time, or get a phone notification when it's done if you've set up ntfy.

Understand the Codebase

9. "Where do we handle password resets?"

Searches the repo and tells you the files and functions involved.

10. "How does the checkout flow decide which payment provider to use?"

Reads the relevant code and explains it in a couple of sentences. These are the questions voice is surprisingly good for: you get the shape of it now, and the details at your desk.

11. "What changed on main since yesterday?"

Summarizes the recent commits.

12. "Which branches have I not touched in a month?"

Lists stale branches, so you know what to clean up later.

Make Small Changes

13. "Fix the typo in the README title and open a draft PR."

Creates a carcode/... branch, makes the change, commits, pushes and opens a draft PR. You'll hear the PR number.

14. "Bump the axios version in the web app and open a draft PR."

Same flow. Draft PRs mean nothing ships until you've reviewed the diff.

15. "Add a test for the date formatting helper."

Good for small, well-defined additions. Anything bigger is better started at your desk, where you can see the plan.

16. "Open an issue: the search box loses focus on mobile."

Reads the issue back first, then creates it after you confirm.

Messages, Email and Your Calendar

These use the connectors you've added to Claude Code, such as Slack, Gmail and Google Calendar.

17. "Anything on Slack mentioning me today?"

Searches your mentions and gives you the gist.

18. "Message Alex that I'll be ten minutes late." → "Confirm."

Reads the exact message back before sending it.

19. "Any important emails since this morning?"

A short summary of what needs you.

20. "What's on my calendar this afternoon?"

Your next meetings, with times.

21. "Reply to the latest email from the design team: I'll review it tonight." → "Confirm."

Drafts the reply, reads it back, and sends only after you confirm.

Research and Thinking Out Loud

22. "What's new in the latest React release?"

Uses web search and summarizes.

23. "Compare Postgres advisory locks with a Redis lock for our job queue."

A short spoken trade-off you can think about for the rest of the drive.

Control the Conversation

24. "Status." · "Cancel."

What it's working on right now, or stop it.

25. "New session." · "Bye."

Start a fresh Claude Code conversation, or end the shortcut.

How to Phrase Things by Voice

• One task per request. "Check CI, then summarize my PRs, then message the team" works better as three turns.
• Name the repo. "On the website repo" saves a clarifying question.
• Say numbers as words. "PR forty-two", not "PR four two".
• Follow up naturally. The session remembers the conversation, so "approve it" or "reply to him" refer to what you were just discussing.
• Trailing off is fine. If dictation cuts you off mid-sentence, carcode says "Go on" and joins the halves.
• Teach it your world once. Put your GitHub username, repo nicknames and teammates in prompts/context.local.md, so "the app repo" and "message Alex" work the first time.

What Not to Do by Voice

• Don't review large diffs. Voice is great for "what changed and is it risky", not for line-by-line review.
• Don't merge anything you haven't seen. The confirm step is a guardrail, not a substitute for reading the code.
• Don't look at the dashboard while driving. carcode has a live dashboard on your phone; it's for passengers, or for after you've parked.

Always follow your local laws on phone use while driving.

Further Reading

• How to Run Claude Code With Siri: setup in five minutes
• Claude on CarPlay vs Claude Code in your car
• How I Code From My Car
• carcode on GitHub

Harsh Rastogi is an AI Product Engineer building generative-AI products and multi-agent systems. He writes about AI systems, developer tooling and production engineering at harshrastogi.tech.