Sahil • gitsu, shareling, gitback

Sahil • gitsu, shareling, gitback

@sahildave.com

Creator coduo.co | gitsu.app | shareling.app | gitback.us

149 followers43 following161 posts

It's been 3 months since Stripe Atlas filed for the EIN. Called the IRS today, and they said they don't have any documents! Stripe has been of no help. We have mobile apps to release but are stuck because of this bureaucratic hellhole! #BuildInPublic #IndieDevs

Did not expect to get such a good response on Threads. Dont sleep on Threads! #BuildInPublic #IndieDevs #GrowthHacking

My favourite way of navigating user journey, understanding implementation completeness and planning the next feature. This pulls data from the app's documentation and my GitHub Projects saved via gitsu.app #BuildInPublic #IndieDevs

Sahil • gitsu, shareling, gitback reposted

Your links are scattered! The links I send @indhuja.bsky.social are all over the place: X, Messages, LinkedIn, Reddit, sometimes WhatsApp. You can't share a bookmark, if you can even find it again. We built something to tackle both. Introducing Shareling: Link sharing for a duo. #BuildInPublic

View full thread

Coming next: - a Chrome extension that brings in your existing bookmarks and saved posts from X, Reddit, LinkedIn and more - iPhone and iPad apps to save and share links on the go #BuildInPublic #indieHacker

View full thread

Search works on meaning, not exact words. Ask for "that dark mode site with the brutalist buttons, built in React" and it turns up. Your library stays private, in your own iCloud. #BuildInPublic #indieHacker

Shareling is a native Mac app for sending links to a person and finding them again later. Drop a link on them at the notch. Keep shared collections for a project, a trip, recipes, lectures. #BuildInPublic #indieHacker

Housekeeping in progress 💙 #BuildInPublic

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: before you let agents loose on your GitHub issues, have Opus send out 𝟯 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then clean up in one pass. ⭐ Prompt to avoid agents burning tokens on tickets that already shipped #BuildInPublic

𝗣𝗮𝘀𝘁𝗲 𝘁𝗵𝗶𝘀 𝗶𝗻𝘁𝗼 𝘆𝗼𝘂𝗿 𝗰𝗼𝗱𝗶𝗻𝗴 𝗮𝗴𝗲𝗻𝘁: “Find every Node install on my machine (which -a node, nvm/fnm/volta, Homebrew, old .pkg installs, tools that bundle their own Node). Upgrade each to a patched version and confirm the node on my PATH is one of them.” nodejs.org/en/blog/vuln... #BuildInPublic

nodejs.orgNode.js — Wednesday, October 21, 2026 Security ReleasesNode.js® is a free, open-source, cross-platform JavaScript runtime environment that lets developers create servers, web apps, command line tools and scripts.

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: before you let agents loose on your GitHub issues, have Opus send out 𝟯 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then clean up in one pass. ⭐ Prompt to avoid agents burning tokens on tickets that already shipped #BuildInPublic

View full thread

Medium effort is enough for the filing and sorting subagents. Run the one that checks shipped issues on high, since it has to read the code. 𝗦𝗲𝗻𝗱 𝘁𝗵𝗶𝘀 𝘁𝗵𝗿𝗲𝗮𝗱 𝘁𝗼 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗮𝗻𝗱 𝗮𝗱𝗱 𝘁𝗵𝗶𝘀 𝗹𝗶𝗻𝗲 𝗮𝘁 𝘁𝗵𝗲 𝗲𝗻𝗱 👇

"One subagent per group. Don't change anything. Show me what you'd close, grouped by reason, with links and evidence. Close only what I approve, in one script. Then give me a table of what's left: milestone, priority, agent or human." DM me for the full skill, isn't public yet.

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: before you let agents loose on your GitHub issues, have Opus send out 𝟯 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then clean up in one pass. ⭐ Prompt to avoid agents burning tokens on tickets that already shipped #BuildInPublic

View full thread

𝗔𝗴𝗲𝗻𝘁𝘀 𝗳𝗼𝗿𝗴𝗲𝘁 𝘁𝗼 𝗳𝗶𝗹𝗲 𝘁𝗶𝗰𝗸𝗲𝘁𝘀 → Read handoff docs and recent commits for TODOs and "follow-up" notes that never became an issue → File each one, linked to where you found it. Avoid over-engineer or pre-mature optimizations.

𝗪𝗵𝗮𝘁'𝘀 𝗹𝗲𝗳𝘁 → Give every open issue a milestone and a priority. Count how many have neither, which is usually the real story → Mark each one "ready for agent" or "needs a human" (sign-off, live keys, a manual pass, UI QA)

𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝘁𝗶𝗽: before you let agents loose on your GitHub issues, have Opus send out 𝟯 𝘀𝘂𝗯𝗮𝗴𝗲𝗻𝘁𝘀 to check 𝘁𝗵𝗲𝘀𝗲 𝟭𝟬 𝘁𝗵𝗶𝗻𝗴𝘀, then clean up in one pass. ⭐ Prompt to avoid agents burning tokens on tickets that already shipped #BuildInPublic

→ Read the acceptance criteria, not just the code. A file existing doesn't mean the ticket is done → A design ticket closes on a screenshot next to the design board. I had 55 tasks passed on test, then found a Settings footer nowhere in the Settings.

→ Every close gets its evidence in the comment: a file:line, a commit, or the criterion now met → Title-only issues are often filed from inside the app while dogfooding. Ask who filed them before closing any

Sahil • gitsu, shareling, gitback reposted

Replying to @sahildave.com

Milestone clarity matters when machines write faster than you can review. My rule: ship features only after three real users ask for them.

Based on a feedback, we've added easier Milestone management for GitHub issues in Gitsu. It gives much needed clarity on your project when AI is implementing your tickets at such a high pace! #BuildInPublic #IndieHacker

I have been trying to use Doop with Codex, but it ALWAYS shows up without any CSS on its canvas. I end up asking Codex to generate screenshots after it finishes the design. Anyone else using it? #BuildInPublic #IndieHackers #UXDesign