# AI use cases for Better Claude (midudev/better-claude) Repo: [midudev/better-claude](https://github.com/midudev/better-claude) | Use cases: 4 | Page: https://dedupedai.com/use-cases/midudev-better-claude/ A set of plugins and mods by midudev that add small features to Claude Code, such as image previews, usage meters, commit helpers and spoken turn summaries. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Split your changes into clean Conventional Commits: https://dedupedai.com/use-cases/midudev-better-claude/split-changes-into-conventional-commits/ - Hear what Claude did after each turn: https://dedupedai.com/use-cases/midudev-better-claude/hear-claude-summarize-each-turn/ - Watch your 5-hour and weekly usage at a glance: https://dedupedai.com/use-cases/midudev-better-claude/track-subscription-usage-windows/ - Check which pasted screenshot a prompt refers to: https://dedupedai.com/use-cases/midudev-better-claude/check-which-screenshot-a-prompt-used/ ## How to split your changes into clean Conventional Commits with Better Claude Repo: [midudev/better-claude](https://github.com/midudev/better-claude) | Difficulty: Intermediate | Time: 15 minutes | Basis: From the README Use /commit to group pending edits into Conventional Commits and push, commit only, or branch. **Who it is for:** A developer with a messy working tree of several unrelated edits who wants clear commit history without writing each message by hand. **The problem:** Writing separate, well-labeled commits for a batch of mixed changes takes time and is easy to skip. **The outcome:** Your pending changes are split into Conventional Commits, and you choose whether to push, commit only, or create a new branch. ### Steps 1. Run `/plugin marketplace add midudev/better-claude` in Claude Code. 2. Run `/plugin install commit@better-claude`. 3. Make some changes in a git repository, then run `/commit` in Claude Code. 4. Choose commit and push, commit only, or a new branch when asked. 5. Review the split commits and messages that Claude proposes before you accept them. ### Prompt to paste into your agent ```text In the git repository at , with the better-claude commit plugin installed, run /commit and choose commit only. Expected output: one or more Conventional Commits covering the pending changes. Verify with git log that each commit message starts with a Conventional Commits type such as feat, fix or docs. ``` ### Caveat The README does not describe how the commit split decides grouping, so review the proposed commits before accepting them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/midudev-better-claude/split-changes-into-conventional-commits/ ## How to hear what Claude did after each turn with Better Claude Repo: [midudev/better-claude](https://github.com/midudev/better-claude) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Turn on Narrator to have Claude speak a summary of each turn in your language. **Who it is for:** A developer who wants to keep an eye on long Claude Code runs without staring at the screen, for example while doing something else in the room. **The problem:** Long agent turns are hard to follow when you are away from the terminal, and you may miss what changed. **The outcome:** After each turn Claude speaks a summary of what it did, using the best free voice your system has. ### Steps 1. Run `/plugin marketplace add midudev/better-claude` in Claude Code. 2. Run `/plugin install narrator@better-claude`. 3. Run `/narrator` or click `⏸︎ narrator off` in the footer to turn narration on. 4. Send a prompt and let Claude finish a turn. 5. Listen for the spoken summary, and use the same control to pause it. ### Prompt to paste into your agent ```text In a Claude Code session with the better-claude narrator plugin installed, run /narrator to turn it on, then send the prompt 'list the files in '. Expected output: a spoken summary after the turn in the language used in the session. Verify that the summary matches what Claude actually did in that turn. ``` ### Caveat The voice depends on what your system provides, so the quality and language of the spoken output may vary by machine. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/midudev-better-claude/hear-claude-summarize-each-turn/ ## How to watch your 5-hour and weekly usage at a glance with Better Claude Repo: [midudev/better-claude](https://github.com/midudev/better-claude) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Install Sub Meter to see subscription usage bars in the bottom right of Claude Code. **Who it is for:** A Claude subscriber who runs heavy sessions and wants to know how much of the 5-hour and weekly windows is left before work stops. **The problem:** Without a visible meter, it is hard to tell how close you are to a usage window limit until you hit it. **The outcome:** You see the 5-hour and weekly usage windows as bars in the bottom right of Claude Code. ### Steps 1. Run `/plugin marketplace add midudev/better-claude` in Claude Code. 2. Run `/plugin install sub-meter@better-claude`. 3. Look at the bottom right of the Claude Code window. 4. Check the bar for the 5-hour window and the bar for the weekly window. 5. Plan heavy runs around the bars you see. ### Prompt to paste into your agent ```text In Claude Code on a subscription account with the better-claude sub-meter plugin installed, check the bottom right of the window for the 5-hour and weekly usage bars. Expected output: two bars showing current usage in each window. Verify that both bars are visible after restarting the session. ``` ### Caveat The README does not say how often the bars refresh, so do not treat them as a live real-time count. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/midudev-better-claude/track-subscription-usage-windows/ ## How to check which pasted screenshot a prompt refers to with Better Claude Repo: [midudev/better-claude](https://github.com/midudev/better-claude) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Hover a pasted [Image #N] tag to see the picture while you write or review prompts. **Who it is for:** A developer who pastes several screenshots into one Claude Code prompt and needs to confirm which image each reference points to. **The problem:** With several [Image #N] tags in a prompt, it is hard to remember which picture each number means. **The outcome:** Hovering a pasted [Image #N] shows the picture, both while writing and on prompts you already sent. ### Steps 1. Run `/plugin marketplace add midudev/better-claude` in Claude Code. 2. Run `/plugin install image-preview@better-claude`. 3. Paste two or more images into a prompt so that [Image #1] and [Image #2] appear. 4. Hover over [Image #1] and [Image #2] to confirm each picture. 5. Hover over the same tags on a prompt you already sent to review it. ### Prompt to paste into your agent ```text In Claude Code with the better-claude image-preview plugin installed, paste two screenshots into a prompt that refers to [Image #1] and [Image #2]. Expected output: hovering each tag shows the matching picture. Verify that each tag shows the correct image before sending. ``` ### Caveat The preview only works on pasted [Image #N] tags as described in the README, so images added another way may not show. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/midudev-better-claude/check-which-screenshot-a-prompt-used/