- Voice (Wispr Flow)
- Type or paste
With Wispr Flow running, just start speaking. Your words appear as text in Claude Code automatically. Describe what you want naturally — Claude Code understands and writes the code for you. Speaking works especially well for long, descriptive prompts because you can talk through the requirements as if explaining to a colleague.
How to Talk to Claude Code
The conversation loop is always the same: Let’s start building.Prompt 1: Describe the Whole Project
Before writing any code, give Claude Code the big picture. This helps it make better decisions at every step. Open your terminal,cd into your daily-report-bot folder, and type claude to start Claude Code. Then say or send this prompt:
Say this or copy this prompt
package.json, a main script file (e.g. index.js or src/index.js), and possibly a config file. It sets up the basic project structure without filling in the logic.
View the generated project structure
View the generated project structure
Claude Code will typically create something like:The exact structure may vary — that’s fine. Claude Code is making reasonable decisions based on your description.
Prompt 2: Build the Commit Collector
Now let’s build the first real piece — the script that reads your git commits.Say this or copy this prompt
git log with the right format string, parses the output, and returns a clean array of commit objects.
Speaking technical prompts works well. Wispr Flow handles technical terms like “git log”, “API”, and “environment variable” accurately. If it mishears something, you can quickly correct the text before pressing Enter.
View the generated code
View the generated code
Prompt 3: Add the Smart Distribution (Commit Banking)
This is the cleverest part of the bot. If you do all your work on Monday, you don’t want Tuesday through Friday to report “nothing done.” Commit banking spreads your commits across the week.Say this or copy this prompt
How commit banking works in practice
How commit banking works in practice
Here’s what happens in a real week:
Every day has something to report, even if you didn’t commit that day.
View the generated code
View the generated code
Prompt 4: Add the AI Summariser
Now we connect to OpenAI to turn raw commit messages into a friendly daily update.Say this or copy this prompt
- What you asked
- What Claude Code built
You described the behaviour — take commits in, get a friendly summary out. You specified the model, tone, format, and how authentication works.
View the generated code
View the generated code
Prompt 5: Add Slack Posting
Time to connect the output to Slack.Say this or copy this prompt
View the generated code
View the generated code
Prompt 6: Wire It All Together and Test Locally
The last build step — connect all the pieces and add a dry-run mode for safe testing.Say this or copy this prompt
View the generated code
View the generated code
Using Claude in Chrome to Research
Sometimes you need to look something up — Slack’s webhook format, GitHub Actions syntax, or an error message. That’s where Claude in Chrome comes in.- Research with Claude in Chrome
- Apply with Claude Code
- Open the Slack API docs or any documentation page in Chrome
- Click the Claude in Chrome extension icon
- Ask it to explain what you’re reading, e.g.: “What format does Slack expect for incoming webhook messages?”
- Use the answer to refine your next prompt to Claude Code
Communication Tips Summary
Be specific about what you want
Be specific about what you want
Instead of “build a Slack bot”, say “build a function that sends a POST request to a Slack incoming webhook with a formatted message using blocks.” The more specific, the fewer iterations.
Give context about your situation
Give context about your situation
Start with the big picture. Tell Claude Code what the project is, who it’s for, and what tools you’re using. Context helps it make better decisions about architecture, naming, and dependencies.
Speaking works well for describing features
Speaking works well for describing features
When using Wispr Flow, don’t worry about speaking technical terms — it handles words like “API”, “webhook”, “JSON”, and “environment variable” accurately. Speaking is especially natural for describing business logic and desired behaviour.
Ask Claude Code to explain what it did
Ask Claude Code to explain what it did
If you don’t understand the code, ask: “Can you explain what this function does in plain language?” Understanding the code helps you spot issues and write better follow-up prompts.
If something breaks, describe the error
If something breaks, describe the error
Copy and paste the exact error message. Tell Claude Code what you expected to happen and what actually happened. Don’t try to diagnose the problem yourself — let the AI help.
Iterate — refine your request step by step
Iterate — refine your request step by step
Your first prompt rarely produces the perfect result. That’s normal. Review what Claude Code built, identify what’s not quite right, and send a follow-up prompt. Each iteration gets you closer.
Full Data Flow
Here’s how everything connects:Your bot is built! Head to Deploy and test to set up GitHub Actions and see it run for real.