# Six AI coding tools, one for each job

> Cost, context, repo packing, browser debugging, diff review and PR review: one tool each, with the install line.

Source: https://fullbytedeveloper.com/blog/ai-coding-tools-one-per-job
Keyword: STACKPICK
Published: 2026-10-31

Don't install 20 AI coding tools. Pick one per job, use it for a week, then add the next. Here are six, with the install line for each from its own README.

**Warning:** plugins and MCP servers can run code on your machine. Read what each one adds before you install it.

## Know what you spend with ccusage

ccusage reads Claude Code's local logs and shows your token use and cost [1]. Nothing to install, it runs through `npx`:

```bash
npx ccusage@latest
```

You should see a table of usage by day, with tokens and an estimated cost for each.

## See your context with Claude HUD

Claude HUD adds a status line to Claude Code that shows how full the context window is and what's running [2]. It installs as a plugin. Inside Claude Code, run these one at a time:

```text
/plugin marketplace add jarrodwatts/claude-hud
/plugin install claude-hud
/reload-plugins
/claude-hud:setup
```

You should see the HUD appear at the bottom of the Claude Code screen.

## Give AI the whole repo with Repomix

Repomix packs a repository into one file you can hand to any AI model [3]. Run it in the repo's root:

```bash
npx repomix@latest
```

You should see a new `repomix-output.xml` in the current folder. To keep using it, `npm install -g repomix` or `brew install repomix` installs it for good [3].

## Debug in real Chrome with Chrome DevTools MCP

The Chrome DevTools MCP server lets Claude Code open Chrome, read the console and network, and check what it built [4]:

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

You should see `chrome-devtools` listed when you type `/mcp` in Claude Code.

## Review the diff with lazygit

Before you commit what an agent wrote, read it. lazygit is a terminal UI for git that makes the diff quick to scan and stage [5]:

```bash
brew install lazygit
lazygit
```

Run `lazygit` inside a git repository. You should see files, branches and the diff in panes.

## Review every PR with Claude Code Action

The Claude Code GitHub Action reviews pull requests and answers `@claude` mentions [6]. The quickest setup is from Claude Code itself, as a repository admin:

```text
/install-github-app
```

It walks you through installing the GitHub app and adding the secret. This path is for direct Anthropic API users; Bedrock, Vertex and Foundry have their own setup in the repo's docs [6].

That's one tool for each job. Add one this week and leave the rest until it earns its place.

## Sources

1. [ccusage README](https://github.com/ryoppippi/ccusage)
2. [Claude HUD README](https://github.com/jarrodwatts/claude-hud)
3. [Repomix README](https://github.com/yamadashy/repomix)
4. [Chrome DevTools MCP: client configurations](https://github.com/ChromeDevTools/chrome-devtools-mcp/blob/main/docs/client-configurations.md)
5. [lazygit README](https://github.com/jesseduffield/lazygit)
6. [Claude Code Action README](https://github.com/anthropics/claude-code-action)

## Original posts

- [TikTok video](https://www.tiktok.com/@fullbytedeveloper/video/7702739204341566740)
- [Instagram reel](https://www.instagram.com/fullbytedeveloper/reel/DfJryQHji6x/)
- [Facebook reel](https://www.facebook.com/reel/29030543023247323/)
- [Instagram post](https://www.instagram.com/fullbytedeveloper/p/DfG45fOG2iP/)
- [TikTok photos](https://www.tiktok.com/@fullbytedeveloper/photo/7702336709505125653)
- [Facebook post](https://www.facebook.com/permalink.php?story_fbid=pfbid02RssYzYQZwrjSiABPJ7sf67rGeg8KUeiPTqgDLGQxYZi4Nu8fvMuDUeofBLRnuBzLl&id=61575497175979)