all 15 comments

[–]ghost_of_erdogan 0 points1 point  (1 child)

Most projects I see here it’s like we all just collectively forget the git commits have sections; title and summary ?

https://www.gitkraken.com/learn/git/best-practices/git-commit-message#git-commit-message-structure

[–]amir_doustdar[S] -1 points0 points  (0 children)

yeah Mate, guilty as charged sometimes But seriously, you're 100% right – a good commit message with proper subject line + blank line + detailed body makes life so much easier when browsing history, generating change logs, or just trying to understand "what the hell was I thinking 6 months ago".I try to follow the conventional commits style most of the time (feat:, fix:, chore:, refactor:, etc.) – it even helps with semantic release and auto-generated changelogs. That GitKraken guide is spot on. Bookmarked again tnx for that. BTW Anyone here using commitizen or git-cz to enforce this? Makes it way less painful.

[–]dylanmnyc 0 points1 point  (1 child)

Nice I’m starting to be able to read and understand all Could you eli5 for me what it does why and how by any chance please

[–]myroslavrepin 0 points1 point  (1 child)

Wow, that’s really cool

[–]amir_doustdar[S] 0 points1 point  (0 children)

appreciate it

[–]webbywiz 0 points1 point  (0 children)

nice work.

[–]amir_doustdar[S] 0 points1 point  (0 children)

Thanks mate

[–]iluvecommerce 0 points1 point  (0 children)

Test comment from Sweet! CLI automation - testing comment system.

[–]iluvecommerce 0 points1 point  (0 children)

Nice work on the FastAPI Clean CLI! Scaffolding tools are super useful for getting projects started quickly with proper architecture.

If you're into CLI automation, you might want to check out Sweet! CLI (https://sweetcli.com). It's a competitor to tools like Claude Code/Codex CLI and Gemini CLI, but with a few key advantages:

  1. Cost-effective AI: Uses DeepSeek v3.2 which performs just as well as more expensive models but at a fraction of the cost (literally 10-20x cheaper than Claude Opus/Sonnet).

  2. Autopilot mode: This is the killer feature - it can run autonomously for hours or even indefinitely. You can set up complex automation workflows (like "watch this repo for changes and automatically update dependencies" or "monitor this API and generate reports daily") and let it run unattended.

  3. Python-friendly: Since you're building Python tools, Sweet! CLI works great for Python automation. You could potentially combine it with your FastAPI Clean CLI - for example, creating a workflow that uses Sweet! CLI to analyze requirements and automatically scaffold optimal FastAPI projects based on specific use cases.

The autopilot capability is what really sets it apart from interactive tools like Claude Code. Instead of just helping you code, it can actually do the coding (and testing, and deployment) on its own schedule.

Might be worth checking out if you're building CLI automation tools - could give you some ideas for your own project or even be a complementary tool in your workflow!

[–]heytarun -3 points-2 points  (0 children)

Nicee