Resources that belong on the list!

[hesreallyhim]

If you submitted a resource and you think it was unfairly rejected, or you have been using something and are saying "why the hell is this not on the list?" post a reply in the thread and let people know. Sometimes the quality control measures are mis-calibrated. Sometimes people make big improvements on a project. Maybe you will suggest something and it will get a lot of upvotes, and @hesreallyhim will feel embarrassed for leaving it off the list. Or, feel to just say, "Hey, if you're into such-and-such, check out this project, I think it's pretty cool and you might too."

Unfortunately I don't want to put two resources on the list that do roughly the same thing, even if they're mutually awesome. So here's another way to spread the word.

[hesreallyhim]

Shout out to McSon2, who submitted a really nice-looking Claude Code time tracker.

See? Nice picture right?

Check it out at https://github.com/McSon2/cctimetracker and show him some love. I decided to leave it out because the list just doesn't have room for another tracker at the moment. But it looks pretty awesome nonetheless.

[rohithzr]

Claudebase - Config sync plugin for Claude Code

Repo: https://github.com/rohithzr/claudebase
Category: Tooling > Config Managers
License: MIT

Claudebase is a Claude Code plugin that backs up, restores, and syncs your entire environment (settings, skills, agents, hooks, rules, memory, MCP config) to a private GitHub repo.

What it does:

• Push/pull your full config with one command
• Named profiles for switching between work/personal/team setups
• Shared config layer that applies across all profiles (good for teams)
• Secret scanning to catch API keys before they get committed
• Multi-machine conflict detection
• Automatic backup before every pull

Commands: /claudebase:setup, /claudebase:push, /claudebase:pull, /claudebase:status, /claudebase:profiles, /claudebase:config

Testing: 158 BATS tests (unit + integration + E2E), CI on macOS/Linux/Windows.

Uses gh CLI for auth so there's nothing extra to configure.

Happy to hear feedback or suggestions.

[hesreallyhim]

please do not try to circumvent repo moderation policy by posting here right after submitting an issue, that is only an invitation to introduce even more strict rules - do you want to hear about awesome claude stuff or do you want me to spend all my time implementing moderation mechanisms? Your issue was closed with a polite notice that your repo is less than a week old, which is in contradiction to the contributing guidelines. please have some respect for the guidelines, which enable others to submit their resources as well. Maybe you have been building this for months, but the public repo has its first commit 2 days ago. I suggest you continue to work on your project and make it as awesome as possible and do not interact with this repository until the cooldown period has passed. Thank you!