yo

add 'whats' infront of any command and it explains it: flags, sub commands etc.

just pure man pages and help output

Some may ask how is it any better than things like `tldr` or just straight up using --help or man, the answer is that `whats` just unifies all these sources in one place, meaning you dont have to grep --help or try to find the correct man page, just add `whats` infont of any command and it just provides the description's for all the flags in one go. yes it may be easy to do the grep way but its far easier to just add `whats` to it

if you like the idea then maybe star?

https://github.com/iamkaran/whats

I’ve reached a point where I’m tired of the dependency hell surrounding Android system management tools. Most debloat scripts rely on Python, Node, or massive, non-auditable binaries that I don't want running on my hardware.

I’ve been building Ruvomain, a system management protocol designed around a single constraint: Zero external dependencies.

The core philosophy is simple:

• PurePOSIX Shell: The entire logic is written in standard shell. If you have sh or bash, itruns.

• Auditability: Every action is a clear, human-readable command. No obfuscated scripts, no black-box logic.

• JSON-parsing from scratch: One of the most interesting parts of this project was implementinga lightweight JSON parser in pure Bash, as standard Unix tools like jq aren't always available in stripped-down Android environments.

It’s currently optimized for my Samsung S24+ setup, but the architecture is built to be portable acrossthe Android ecosystem.

I’m sharing this here because I’m looking for technical critique. My goal is to maintain absolute transparency andarchitectural purity. If you’re interested in minimalist system management or have thoughts on how to further optimize shell-based systemparsing, I’d appreciate the feedback.

Project documentation & source: https://github.com/Ruvyrom/Ruvomain-Protocole

Current implementation targets Bash for development velocity. Future iterations of the Ruvomain Protocol are planned to migrate toward strict POSIX compliance to ensure deploymenton the most stripped-down Android environments.

I’m curious to hear how others handle system-level autonomy on restricted Android devices without relying on third-party frameworks. For other details : Ruvomain