DEV Community: Bharathkumar

[Boost]

Bharathkumar — Mon, 16 Feb 2026 18:47:50 +0000

GitHub Copilot CLI Challenge Submission

Bharathkumar

Feb 16

snip - Terminal Snippet Manager

#devchallenge #githubchallenge #cli #githubcopilot

Comments 1

1 min read

snip - Terminal Snippet Manager

Bharathkumar — Mon, 16 Feb 2026 07:18:16 +0000

This is a submission for the GitHub Copilot CLI Challenge

What I Built

snip is a CLI snippet manager that lets developers save, search, and safely execute code snippets directly from the terminal—with fuzzy search, a keyboard-first TUI, and GitHub Gist sync.

Demo

My Experience with GitHub Copilot CLI

Copilot CLI was like having a senior dev sitting next to me the entire time. When I got stuck on weird sql.js errors or needed to figure out how to make the SQLite adapter work with both better-sqlite3 and the WASM fallback—Copilot just got it. Instead of alt-tabbing to Stack Overflow every 5 minutes, I'd drop a prompt right in my terminal and get usable code back.

Website

https://bharath-code.github.io/snip/
https://github.com/Bharath-code/snip

usage npm

npm i snip-manager or npm install -g snip-manager

git scope -> manage your multi git repos

Bharathkumar — Wed, 17 Dec 2025 18:24:15 +0000

Bharathkumar

Dec 17 '25

How I Built In-App Workspace Switching for Multi-Repo Git Workflows

#git #go #cli #productivity

Comments 1

2 min read

How I Built In-App Workspace Switching for Multi-Repo Git Workflows

Bharathkumar — Wed, 17 Dec 2025 18:21:12 +0000

Why Multi-Repo Git Workflows Break Down

Modern development often means juggling many small repositories:
microservices, shared libraries, tooling repos, and experiments.

Git works extremely well at the single-repo level.
Once you scale beyond that, context is what breaks first.

I kept running into the same issues:

Losing track of which repos were dirty
Jumping between different project trees
Restarting tools just to change directories
Symlinked workspaces behaving inconsistently

This post is a short case study on how that led to git-scope v1.3.0.

Constraints That Shaped the Solution

Before writing code, I set some firm constraints:

Terminal-first
Local-only (no cloud, no telemetry)
Read-only by default
Composes with existing tools (editors, lazygit, shell)

git-scope is intentionally a lens, not a control panel.

Why Workspace Switching Was Necessary

Originally, git-scope relied on configured root directories.
That worked until real workflows got messy.

Switching contexts meant:

Quitting the app
Editing config
Restarting

That breaks flow.

v1.3.0 introduces in-app workspace switching so you can move between
repo trees without restarting or reconfiguring anything.

Handling Real-World Filesystems (Symlinks)

Many setups rely on symlinks:

Codespaces
External drives
Dotfile-based workspaces

If cd works, the tool should work.

v1.3.0 resolves paths explicitly so absolute paths, relative paths,
and symlinked directories behave consistently.

What I Deliberately Didn’t Build

Just as important as what shipped is what didn’t:

No git write operations
No file browsing
No team dashboards
No telemetry or background services

The goal is clarity, not control.

Outcome So Far

Workspace switching removed a real daily friction for me.
More importantly, it clarified what git-scope is supposed to be:
a calm overview of many repos, not another git client.

Closing Thoughts

Many teams end up building internal tooling to deal with repo sprawl.
git-scope is my attempt to make one of those tools reusable,
without losing the simplicity that made it useful.

Closing Thoughts

Many teams end up building internal tooling to deal with repo sprawl.
git-scope is my attempt to make one of those tools reusable,
without losing the simplicity that made it useful.

Project: https://github.com/Bharath-code/git-scope

How to use git-scope.

Bharathkumar — Wed, 10 Dec 2025 13:08:27 +0000

Bharathkumar

Dec 10 '25

Git-Scope User Guide

#git #cli #guide #productivity

Comments 1

2 min read

Why I Chose GoatCounter Analytics for my GitHub Pages Site

Bharathkumar — Wed, 10 Dec 2025 09:06:31 +0000

Simple Analytics for GitHub Pages: Why I Chose GoatCounter

Adding analytics to a static site usually ends in one of two ways:

Google Analytics: A privacy nightmare that requires a GDPR cookie banner.
No Analytics: You fly blind and never know if anyone visited.

I needed a middle ground for my GitHub Pages site. I looked at the big three options.

1. Google Analytics (Why Not?)

GA4 is overkill. It tracks everything, sells the data, and forces you to annoy users with cookie consent popups. I just want to know how many people clicked my "Install" button.

2. Cloudflare Web Analytics (Why Not?)

Cloudflare offers great free analytics.
The Problem: It expects you to own the domain.
Because I use a github.io subdomain, I cannot easily proxy my DNS through Cloudflare. Without DNS control, the setup becomes friction. I wanted "drop-in" simplicity.

3. Umami (Why Not?)

Umami is fantastic and open-source.
The Problem: Hosting.
You must self-host it (on Vercel/Railway) and manage a database (Supabase/Postgres). That is too much maintenance for a simple documentation site.

The Winner: GoatCounter 🐐

GoatCounter hit the sweet spot.

Hosted: No server to manage.
Free: Generous tier for non-commercial projects.
Privacy: No cookies. No GDPR banners required.
Universal: Works on any domain, including github.io.

How We Integrated It

The setup took 2 minutes.

Step 1: Get the Code

Step 2: Add the Script

We added a single JS file to our docs/ folder to keep it clean.

docs/index.html:

<script data-goatcounter="https://your-code.goatcounter.com/count"
        async src="count.js"></script>

We host the count.js locally to avoid external dependencies blocking the main thread, though you can load it from their CDN too.
But still it blocked by Brave's adblocker.

💻 Check out the Git-Scope Docs to see it in action.
🌐Site

Git-Scope User Guide

Bharathkumar — Wed, 10 Dec 2025 08:38:33 +0000

Git-Scope User Guide 🔭

Git-Scope is a terminal dashboard for your local git repositories.

Stop cd-ing into folders to check status. Scan your projects and see a real-time dashboard of your entire workload.

📦 Installation

Run these commands:

macOS / Linux (Homebrew)

brew tap Bharath-code/tap
brew install git-scope

Go Install

go install github.com/Bharath-code/git-scope/cmd/git-scope@latest

💻 CLI Commands

Use these commands to control the tool:

git-scope                    # Launch dashboard (default)
git-scope scan               # Print repos as JSON
git-scope scan-all           # Scan entire system from home dir
git-scope init               # Create config file
git-scope -h                 # Show help

Flags:

-config: path to config file (default: ~/.config/git-scope/config.yml)

🖥️ The Dashboard

When you run git-scope:

Columns

Status: ● Dirty (Uncommitted/Unpushed) or ✓ Clean.
Repository: Project folder name.
Branch: Active branch (e.g., main).
Staged: Files ready to commit.
Modified: Changed files.
Untracked: New files.
Last Commit: Time since last commit.

🎮 Controls

Git-Scope is keyboard-first.

Movement

Key	Action
`k` / `↑`	Up
`j` / `↓`	Down
`q`	Quit

🔍 Search

Press / to search.

Types fuzzy match (gscope finds git-scope).
Enter confirms, Esc cancels.

🛡️ Filter (Dirty)

Press f to toggle the Dirty Filter.

ON: Shows only repos with uncommitted or unpushed changes.
Use Case: Find unfinished work instantly.

🔃 Sort

Press s to cycle sort:

Dirty First (Default)
Name
Last Modified

🚀 Actions

Key	Action
`Enter`	Open repo in `$EDITOR`
`r`	Rescan text system
`c`	Clear search

⚙️ Configuration

Git-Scope works instantly. It finds git repos recursively in your current directory.

Run from ~/projects for best results.
Ignores node_modules automatically.

Caching: Git-Scope caches results for speed (<10ms). Press r to refresh if needed.

⚡️ Workflow: Monday Morning Triage

Run git-scope.
Check Sync column for ↓ (behind origin).
Press f to see Dirty repos.
Press Enter to fix them.

Get Started
Star on GitHub | Website

A guide to managing 50+ local git repositories efficiently using Git-Scope, a TUI for polyrepo power users

Bharathkumar — Wed, 10 Dec 2025 08:00:21 +0000

Bharathkumar

Dec 10 '25

How to Tame Your Multi-Repo Chaos with the Terminal

#opensource #go #cli #git

Comments 1

3 min read

How to Tame Your Multi-Repo Chaos with the Terminal

Bharathkumar — Wed, 10 Dec 2025 07:57:29 +0000

As a full-stack developer or SRE, you likely live in a world of microservices and polyrepos.

You have 10, 20, or maybe 50+ repositories cloned locally.

apps/frontend
apps/backend
libs/ui-kit
infrastructure/terraform
...and that one side-project you forgot about.

The Problem: "Context Fatigue" 🛑

Every morning, the ritual is the same. navigate to each folder, checking if you forgot to push changes or if you're behind origin/main.

cd apps/frontend
git status
# nothing to commit
cd ../../libs/ui-kit
git status
# ...

This manual context switching is a productivity killer. It pulls you out of your flow state before you even write a single line of code.

Existing GUIs (like GitHub Desktop or Sourcetree) are often too slow or bloated due to Electron. lazygit is amazing, but it's designed for focusing on one repository at a time, not managing fifty.

The Solution: A "God Mode" Dashboard for Git ⚡️

I needed a tool that was:

Blazing Fast: Instant startup (written in Go).
Terminal First: I don't want to leave my CLI.
Multi-Repo: Shows me the state of all my projects in one view.

So, I built Git-Scope.

Key Features

Recursive Discovery: Automatically finds git repos in your ~/projects folder.
"Dirty First" Sorting: Instantly bubbles up repos with uncommitted changes so you never lose work.
Fuzzy Search: Type / to jump to any project by name.

Who is this for? (ICP & Use Cases)

We built this for the Polyrepo Power User—specifically:

1. The Microservices Backend Engineer 🏗️

Pain: You are working on a feature that spans 5 services (auth, payments, core, etc.). You edited code in 3 of them but forgot which ones.
Solution: Open Git-Scope. The "Dirty" status bubbles all 3 modified repos to the top. You commit and push them in seconds, ensuring your PRs stay in sync.

2. The SRE / DevOps Engineer 🛠️

Pain: You manage dozens of Terraform modules or Ansible roles. You need to check if your local copies are behind origin/main before running a plan.
Solution: One glance at the dashboard shows you exactly which infrastructure repos are out of date (↓ 2 commits behind). You can pull updates without cd-ing into each directory.

3. The Open Source Maintainer 🐙

Pain: You maintain 10+ libraries. You have random stashes and unpushed experimental branches scattered everywhere.
Solution: Use the Fuzzy Search (/) to instantly jump between libraries to review PRs locally. Use the "Clean" filter to find "abandoned" experiments you forgot to delete or push.

How to Install

If you are on macOS or Linux, you can install it via Homebrew:

brew tap Bharath-code/tap
brew install git-scope

Or install directly with Go:

go install github.com/Bharath-code/git-scope/cmd/git-scope@latest

Why I Built This?

I wanted a tool that respects the "Unix Philosophy": do one thing and do it well.

Git-Scope doesn't try to replace git or lazygit. It complements them. It's the high-level radar functionality that was missing from my workflow. It helps me stay in the flow and manage my local git universe without the friction.

Check it out on GitHub and let me know what you think!

👉 GitHub Repository
👉 Website