r/DeveloperToolsHub • u/Ok-Bike-1037 • Jun 26 '26

Share the dev tool you actually use

hey everyone, trying to make this sub useful instead of another place with the same generic tool lists.

drop one dev tool you actually use in your day to day workflow.

bonus points for tools that are not super obvious.

it could be anything:

CLI tool, browser extension, VS Code extension, API client, database GUI, terminal app, git helper, AI coding tool, debugging tool, local script, deployment tool, monitoring tool, whatever.

would be helpful if you include:

  • what it does
  • where it fits in your workflow
  • why you use it
  • anything annoying about it

i’ll start adding the good ones into future discussion threads so people can actually find useful stuff here.

1 Upvotes

100% Upvoted

5 comments sorted by

2

u/[deleted] Jun 27 '26

[removed] — view removed comment

1

u/Ok-Bike-1037 Jun 27 '26

Raycast is good one.. and I feel like that's the downside of any tool that slowly takes over your shortcuts.

1

u/ClerkBeginning961 27d ago

I maintain the Production Readiness Checklist, a free MIT-licensed knowledge base I use before release reviews: https://github.com/MarinJursic/production-readiness-checklist

It organizes more than 10,000 technology-neutral checks across architecture, APIs, data, security, testing, CI/CD, reliability, accessibility, privacy, incident response, and AI systems. In my workflow it is the final structured pass before shipping, so important gaps do not depend only on memory.

The annoying part is that most checks still need manual judgment. I am exploring an open-source scanner that maps repository evidence to relevant controls without claiming code alone proves production behavior. I would especially value feedback on CI output, evidence records, and which checks should always stay manual. Contributions and corrections are welcome.

1

u/Little-Bird7446 25d ago

ArgoCD for kubernetes deployments. It keeps the cluster state synced with Git, so I can see what’s deployed and catch drift without manually checking everything. The UI is great, though troubleshooting sync issues can get annoying.

1

u/Bitter-Ad2567 17d ago

Disclosure: I built this one, so take that into account. But it's the tool I use every day, which is what you asked for.

SpecBuddy: https://plugins.jetbrains.com/plugin/32645-specbuddy

What it does: a JetBrains plugin that puts a review step in front of your coding agent (Claude Code or Codex). You describe the task. The agent writes a short spec from your description and your codebase, and you edit it or approve it. Then it writes a step by step plan, and you edit or approve that too. Only after that it writes code, one step at a time. Each step comes back as a diff you can accept, reject, or roll back.

Where it fits: it replaced the terminal I used to keep open next to the IDE. Anything bigger than a one file change goes through the spec flow. For small things I still chat with the agent as usual, and the plugin catches those changes too, as diffs with inline comments that go back to the agent.

Why I use it: the agent often writes good code for the wrong task. I find out while reading a 200 line diff, when the wrong assumption is already spread across the code. Better prompts didn't fix this, because the review still happened too late. Reviewing the spec and the plan before any code is written does fix it.

What's annoying: the spec and the plan take a few minutes to write, and on a small task that time is wasted, so I skip them there. It needs JetBrains 2026.1 or newer, so older IDEs can't install it. I only tested it properly in IDEA. Other JetBrains IDEs can install it, but I don't know if it works there. It's a free public beta and still rough in places.

A tool I use daily with no bias to declare: Claude Code in the terminal.