I'm Aman Awasthi, a software builder studying Banking & Finance in India.
Alongside my B.Com (Hons.) and CA Foundation preparation, I build developer tools, browser applications and Linux systems. I like work where the details matter: a command that previews its changes, an error that explains what happened, a fix someone else can review.
| Studying B.Com (Hons.) · CA Foundation |
Building AI-workflow CLIs, file tools, a Void Linux desktop |
Contributing Fixes, tests and docs across dev tooling |
| Project | What it does | Stack |
|---|---|---|
| Aetheris OS | Experimental, hardware-aware desktop system on Void Linux, with installation, setup and software-management tools. | Rust C Svelte Tauri runit |
| Aman CLI | One place for your AI workflows: organize skills, prompts and MCP configs, with read-only diagnostics. | TypeScript Node.js |
| Momentum | Expo productivity app for tasks, habits, focus sessions and personal planning. | TypeScript Expo |
| ObsidianKit | Browser-native toolbox for document, image, media, calculator and utility workflows. | React TypeScript Vite |
| Sweepr | Terminal file organizer with dry-run previews and undo manifests. | Python Typer Rich |
I help maintain opencode-mem and awesome-free-apps, and contribute fixes, tests and docs to developer tools.
| 37 | 20 | 138 |
|---|---|---|
| merged PRs in external repos | external repositories | merged PRs overall |
Verified October 25, 2026 · Browse the contribution record →
Currently under review
- reticle #1085:
verify --expect-fileand PowerShell usage docs - ComfyUI_frontend #18817: refuse overwriting existing specs in the test recorder
- less.js #4549: leave
min()/max()intact when args contain CSS vars - claude-devtools #244: preserve scroll position across tab switches
- rtk #4330: stable example command per discover bucket
- helix #16309: selection terminology in docs
- snakemake #4324: correct conda environment storage path docs
- Axl #433: highlight Containerfile, Dockerfile.* and shell dotfiles in the TUI
Open pull requests as of October 25, 2026.
| Understand the failure | Reproduce it before changing the implementation. |
| Make the fix reviewable | Keep changes focused and add regression coverage where it helps. |
| Leave a clear trail | Document actual behavior, explain failures and make changes reversible. |
- Linux desktop latency: find the cause before tuning
- Privacy-first React components: storage and safe defaults
- Using an AI coding CLI: context, permissions and diff review
Have something in mind? Tell me about it →



