Open source · Developer tooling

git-tidy

Making branch cleanup inspectable before deletion

An open-source CLI by Arman for reviewing stale and merged Git branches. It pairs an interactive terminal workflow with dry-run defaults and JSON output for scripts.

Role: Open-source author
Status / period: Independent tool
Explore: Source and documentation ↗

git-tidy Open source / MIT

# Preview merged branches
npx git-tidy-cli --merged --dry-run

# Inspect stale branches as JSON
npx git-tidy-cli --stale 30 --json

Image source & context

Documented usage examples from Arman’s open-source CLI. These are commands, not a simulated execution or a record of deleted branches. Source & usage on GitHub ↗

preview by default: Dry-run
terminal selection workflow: Interactive
structured output for scripts: JSON

Public product context

What the product does.

git-tidy is Arman’s open-source branch-cleanup CLI. Its public repository documents an interactive workflow alongside flags for scripting, allowing a developer to inspect stale or merged branches before removing anything.

Preview before changing a repository

Dry-run behavior makes the candidate branches visible first. Interactive review supports a deliberate choice rather than an automatic destructive sweep.

Use the same tool in a script

Structured JSON output and filtering flags support automation. The repository is the source for its documented commands and MIT license.

Research sources · October 25, 2026

git-tidy · source and usage ↗

The challenge

Branch cleanup needs a clear distinction between identifying candidates and deleting them. A useful tool should let a developer review the selection, while exposing predictable output for automation.

The engagement

Engineering the product.

Preview before execution

Dry-run mode is the default. Actual deletion requires an explicit execution option, making the action visible in the command.

Select by useful criteria

Filter local or remote branches by merged status, staleness, age and name patterns. Combine criteria and review the matching selection.

One tool for people and scripts

An Ink-based interactive interface serves manual cleanup, while non-interactive flags and JSON output support scripts, CI and agent workflows.

Delivered.

Published source and documented CLI usage under the MIT license.
Built interactive and non-interactive paths around explicit preview and execution.

TypeScript · Node.js · React · Ink · GitHub API

An independent open-source project by Plixy’s founder, shown as engineering work rather than a client engagement. Commands in the visual are documented usage examples.