Guides on @zhisme :: signal over noise

Multiple Git Configs Per Directory

Mon, 30 Mar 2026 00:00:00 +0000

The Problem

You have a personal GitHub and a work GitLab (or multiple work accounts). Your global ~/.gitconfig has your personal email. You clone a work repo, make a commit, push — and now your personal email is in the company git history. haha-haha classic..

You could run git config user.email in every new repo you clone. But you’ll forget. You always forget. But this is a boring routine, why do this?

Practical Useful Commands for Claude

Tue, 17 Mar 2026 00:00:00 +0000

These are commands I use often and see a lot of value from. I advise you at least to consider using them in case you haven’t tried them yet.

Commands

claude --worktree or claude -w

In case you want multiple agents to run simultaneously, this option was designed for it. Each Claude agent gets its own version of the repo so they won’t interfere with each other. Where can you use it? Let’s say you’re migrating something to a new architecture and there are multiple services that need changes, but they’re located in a monorepo. With this option, each agent will be moving its own service or “folder” if you want, without getting conflicts with others.

Disable Co-Authored-By Claude in Git Commits

Fri, 27 Feb 2026 00:00:00 +0000

Solution

Open ~/.claude/settings.json with your favorite editor and add this to your json config. This is taken from Claude docs¹

{
 // ...
 "attribution": {
 "commit": "",
 "pr": ""
 }
}

Why

This actually makes no sense and I agree with Rob Pike’s take on that². It just adds non-readable boilerplate that does not add any value to the git commit. If it was committed by some guy I expect him to take responsibility of that commit, not some excuse like “that was written by Claude, sorry I didn’t check”. So it makes no sense at all, we are blind to that string anyway. Git commits should be atomic, simple and readable, not overwhelmed by nonsense. The trick above will help you with that.

How to Set Up Browser MCP in Claude Code

Sat, 24 Jan 2026 00:00:00 +0000

How to set up MCP for browser

Create .mcp.json in your project directory with the following content:

{
 "mcpServers": {
 "chrome-devtools": {
 "command": "npx",
 "args": ["-y", "chrome-devtools-mcp@latest"]
 }
 }
}

Then run the following command in your terminal:

claude mcp add chrome-devtools --scope user npx chrome-devtools-mcp@latest

Then in Claude Code, run /mcp to verify the connection:

# start claude code cli
claude
# run /mcp inside cli
/mcp
─────────────────────────────────────────────────────────────────────────────────
 Manage MCP servers
 2 servers

 Project MCPs (/Users/zhisme/projects/my-project/.mcp.json)
 ❯ chrome-devtools · ✔ connected

Afterwards, run a sample command to verify that the browser MCP can start:

 ▐▛███▜▌ Claude Code v2.1.17
▝▜█████▛▘ Opus 4.5 · Claude Max
 ▘▘ ▝▝ ~/dev/projects/new-magtuner/mt-editor

❯ open with browser mcp url google.com

⏺ chrome-devtools - navigate_page (MCP)(type: "url", url:
 "https://www.google.com")
 ⎿  # navigate_page response
 Successfully navigated to https://www.google.com.
 ## Pages
 1: https://www.google.com/ [selected]

⏺ Opened google.com in the browser. The page is loaded and selected.

If you see a Google Chrome for Testing window like in the screenshot below, then everything is set up correctly. You can now tell Claude to visually verify your rendered pages.

Google chrome via browser mcp