Git-workty – I got tired of Git stash and built a worktree wrapper
I context-switch a lot. Someone pings me about a bug while I'm mid-feature, and I either: 1. `git stash` (and forget what's in there forever) 2. Make a "WIP: stuff" commit (clutters history) 3. Ignore them until I'm done (not great) Worktrees solve this perfectly – each task gets its own directory, fully isolated. But the commands are clunky and I kept forgetting the syntax. So I built a small CLI wrapper. Now my workflow is: ``` wnew feat/login # creates worktree + cd into it # ...do work... wcd # fuzzy-pick another worktree, cd there wgo main # jump straight to main ``` Dashboard…
Git-workty – I got tired of Git stash and built a worktree wrapper launched on January 6, 2026 with 7 votes, #1,609 of 14,584 launches that month and more than 75% of that year's launches.
What it does
Git worktrees as daily-driver workspaces. Contribute to binbandit/workty development by creating an account on GitHub.
I got mass-context-switching burnout. Every git stash felt like shoving clothes under the bed before guests arrive. WIP commits? "WIP: stuff" cluttering my history. Worktrees fixed it, but the raw commands are clunky. So I built this. Now I just wnew feat/login , do the work, wcd back to main when someone pings me about a bug, fix it, and wcd right back. No stashing. No mental overhead. $ git workty ▶ feat/login ● 3 ↑2↓0 ~/.workty/myrepo/feat-login main ✓ ↑0↓0 ~/src/myrepo hotfix-auth ● 1 - ~/.workty/myrepo/hotfix-auth Install cargo install git-workty Then add shell integration (so wcd , wnew , wgo actually change your directory): git workty install-man This will write git-workty.1 to…from github.com
In the maker’s words, at launch
I context-switch a lot. Someone pings me about a bug while I'm mid-feature, and I either: 1. `git stash` (and forget what's in there forever) 2. Make a "WIP: stuff" commit (clutters history) 3. Ignore them until I'm done (not great) Worktrees solve this perfectly – each task gets its own directory, fully isolated.…
Does a similar job
all alternatives →
I made a tool that made me faster at Git2018 · github.com · ▲551simple terminal UI for git commands. Contribute to jesseduffield/lazygit development by creating an account on GitHub.
Lazyworktree, a TUI manager for Git worktreesJan 2026 · github.com · ▲9Inspired by lazygit, I have been working on a TUI to manage git worktrees easily, making some workflows for creating and managing worktrees a bit more straightforward. For example, creating a worktree from a PR/MR or from local changes. Executing commands on a worktree, or running a custom tmux session directly on a selected worktree. A lot of other tools are more CLI-oriented. I have tried to compile an honest comparison here: https://github.com/chmouel/lazyworktree/blob/main/COMPARAISO... Some of the code and documentation was written with an LLM if…
"Git who" – A new CLI tool for industrial-scale Git blaming2025 · github.com · ▲252I've always wanted a better way to explore the authorship data embedded in a Git commit log. I'm having fun building a CLI tool to do this. It's a bit like the "Contributors" tab on Github that shows you how many commits each contributor has made but much faster and with many more options. If you get a chance to try it out, please let me know. I'd love to hear feedback and suggestions. Thank you!
diny2025 · github.com · ▲175Hi everyone, I built a CLI tool called *diny* that generates Git commit messages directly from your staged changes. - It runs `git diff` and filters out noise like lockfiles, build artifacts, and binaries. - From the cleaned diff it suggests a clear commit message. - You can confirm or refine the message before committing. Key points: - No setup or API keys required. - Lightweight, local-first workflow. - Supports different lengths and styles (short, normal, long; conventional or simple). - Built in Go with Cobra for a familiar CLI experience. Repo:…

Gitin – a minimal commit/branch/workdir explorer for Git2019 · github.com · ▲107commit/branch/workdir explorer for git. Contribute to isacikgoz/gitin development by creating an account on GitHub.
More dev tools this month
the category →

Contribute to oosexgang/hackios-xnu-kernel development by creating an account on GitHub.
Dev tools · 22h ago · github.com

open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 29d ago · github.com

Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 27d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 24d ago · openbot.run
Talanoa▲346Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 22d ago · talanoa.email
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, January 2026
the whole month →- IN
Hey HN! I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents. I didn't write a single line of code. Of course no-code doesn't mean no-engineering. This project took a lot more manual labor than I'd hoped! I wrote a deep dive on the workflow and some thoughts about the future of AI coding and creativity: http://cannoneyed.com/projects/isometric-nyc
AI · Jan 2026 · cannoneyed.com




Automatic AI-powered code reviews the moment you open a PR
Dev tools · Jan 2026 · kilo.ai
