# AI use cases for Claude Code Tips Tricks (onmyway133/claude-code-tips-tricks) Repo: [onmyway133/claude-code-tips-tricks](https://github.com/onmyway133/claude-code-tips-tricks) | Use cases: 4 | Page: https://dedupedai.com/use-cases/onmyway133-claude-code-tips-tricks/ A personal collection of Claude Code tips and tricks, covering sessions, effort levels, scripted runs, subagents, skills, hooks, MCP, and workflow habits. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Resume a multi-day feature in a named Claude Code session: https://dedupedai.com/use-cases/onmyway133-claude-code-tips-tricks/resume-named-claude-code-sessions/ - Learn an unfamiliar module with Explanatory output style: https://dedupedai.com/use-cases/onmyway133-claude-code-tips-tricks/study-unfamiliar-codebase-explanatory-mode/ - Run a recurring PR check on a timed loop: https://dedupedai.com/use-cases/onmyway133-claude-code-tips-tricks/schedule-recurring-pr-cleanup-loop/ - Speed up Claude Code calls in scripts with --bare: https://dedupedai.com/use-cases/onmyway133-claude-code-tips-tricks/run-claude-in-scripts-with-bare/ ## How to resume a multi-day feature in a named Claude Code session with Claude Code Tips Tricks Repo: [onmyway133/claude-code-tips-tricks](https://github.com/onmyway133/claude-code-tips-tricks) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Name each workstream with /rename and pick it back up later with claude --resume. **Who it is for:** A developer working on one feature across several sittings who keeps losing context between sessions. **The problem:** Re-explaining a multi-day task from scratch every time a new session starts wastes time and context. **The outcome:** Each feature has its own named session, and you can return to it with the earlier context still there. ### Steps 1. Start Claude Code in the project folder with `claude`. 2. Run `/rename` and give the session a descriptive name, such as oauth-migration. 3. When you come back later, run `claude --resume` and pick the session by name from the list. 4. Or run `claude --continue` to jump straight back into your most recent session. ### Prompt to paste into your agent ```text In the Claude Code repo at , name the current session for the workstream using /rename, then confirm the name appears when you run claude --resume. Report the session name you set and whether it appears in the list. ``` ### Caveat This is a personal tips collection rather than official documentation, so check the linked Claude docs for current session behavior. 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/onmyway133-claude-code-tips-tricks/resume-named-claude-code-sessions/ ## How to learn an unfamiliar module with Explanatory output style with Claude Code Tips Tricks Repo: [onmyway133/claude-code-tips-tricks](https://github.com/onmyway133/claude-code-tips-tricks) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Switch Claude Code to Explanatory mode and have it walk through a module as it works. **Who it is for:** A developer onboarding onto a codebase they did not write and needing to understand a tricky module. **The problem:** Reading unfamiliar middleware or patterns cold is slow, and the code alone does not explain why it is built that way. **The outcome:** Claude explains the frameworks and patterns behind the module, giving you a guided walkthrough of the code. ### Steps 1. Run `/config` and set the output style to Explanatory. 2. Start Claude Code in the repository you are studying with `claude`. 3. Ask for a walkthrough of one module, for example: Walk me through how the request middleware pipeline works in @src/server/middleware, explaining the pattern as you go. 4. Ask follow-up questions on any step that does not yet make sense. ### Prompt to paste into your agent ```text In the repo at , with the output style set to Explanatory, walk through the module at and explain its main pattern. Expected output: a step-by-step explanation naming the key files. Verify by checking that each named file exists in the repo. ``` ### Caveat The README describes output styles as a setting in /config, so the exact menu labels may differ in your version of Claude Code. 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/onmyway133-claude-code-tips-tricks/study-unfamiliar-codebase-explanatory-mode/ ## How to run a recurring PR check on a timed loop with Claude Code Tips Tricks Repo: [onmyway133/claude-code-tips-tricks](https://github.com/onmyway133/claude-code-tips-tricks) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Use /loop to repeat a task on an interval so you do not trigger it by hand each time. **Who it is for:** A team lead or maintainer who wants open pull requests checked regularly without remembering to do it. **The problem:** Routine PR babysitting and cleanup gets skipped when it depends on someone starting it manually. **The outcome:** A task repeats on your chosen interval for up to three days while you work on other things. ### Steps 1. Write the recurring workflow as a skill, for example one named pr-pruner (inferred: the README uses this name as an example). 2. Start Claude Code in the repository with `claude`. 3. Run `/loop 1h /pr-pruner` to repeat the skill every hour. 4. For a shorter check, run `/loop 5m /babysit` instead. 5. For a job that keeps running after you close your laptop, use `/schedule` as the README describes. ### Prompt to paste into your agent ```text In the repo at , set up a loop that runs the pr-pruner skill every hour using /loop 1h /pr-pruner. Expected output: the loop starts and reports its interval. Verify by confirming the loop status shows the 1h interval. ``` ### Caveat The README says /loop runs for up to three days, so plan to restart it for longer-running work. 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/onmyway133-claude-code-tips-tricks/schedule-recurring-pr-cleanup-loop/ ## How to speed up Claude Code calls in scripts with --bare with Claude Code Tips Tricks Repo: [onmyway133/claude-code-tips-tricks](https://github.com/onmyway133/claude-code-tips-tricks) | Difficulty: Advanced | Time: 45 minutes | Basis: From the README Pass the --bare flag with explicit config so scripted runs skip local file discovery. **Who it is for:** A developer or CI maintainer calling Claude Code from a script where the inputs are already known. **The problem:** Claude Code searches the filesystem for CLAUDE.md, settings, and MCP configs before every run, which slows down scripted use. **The outcome:** Scripted runs start faster because they load only the config you pass in explicitly. ### Steps 1. Decide which system prompt, MCP config, and settings the script needs. 2. Pass them explicitly with --system-prompt, --mcp-config, and --settings. 3. Run `claude -p "summarize this codebase" --output-format=stream-json --verbose --bare` from your script. (inferred, check the README) 4. Check that the output stream arrives and that the run starts faster than before. ### Prompt to paste into your agent ```text In the repo at , run claude -p with --bare and explicit --system-prompt, --mcp-config, and --settings values to summarize . Expected output: a stream-json summary of the codebase. Verify that the command exits successfully and that no CLAUDE.md file was loaded by discovery. ``` ### Caveat The README says the local file search default may change in a future version, so re-check the --bare behavior after updates. 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/onmyway133-claude-code-tips-tricks/run-claude-in-scripts-with-bare/