I learned coding this week and I made vim

I learned coding this week and I made vim

Well, not exactly vim. But I built something guided by the same philosophy: workflow is automation, not creation.

While learning Python, I kept hitting the same friction points that every developer faces - git is overkill for solo work, changelogs are tedious, command histories get messy, notes are scattered everywhere.

So I built a terminal-native productivity suite that removes these frictions:

• gitnot - “git for individuals” with simple checkpoints instead of branches
• chng - AI-powered changelog generation from diffs
• ql - interactive command launcher for frequently-used commands
• mdns - file manager that ties everything together
• 5 other tools that each solve exactly one workflow problem

The insight: most productivity software tries to do everything. I built tools that do one thing excellently and integrate seamlessly.

Each tool follows the same principles:

• Terminal-native but approachable UX
• Works with plain text/markdown files
• Solves exactly one friction point
• No configuration complexity

After a week of using this ecosystem, I’m convinced that good workflow tools should feel invisible - like vim does for text editing.

Source: github

I’m after genuine feedback. Roast away.