Multi-repository workspace management

uman manage many repositories with one consistent CLI.

Uman Manages Apps Nicely. Inspect Git status, run commands across projects, check workspace scaffolding and licensing, and preview or publish project websites from one configured workspace.

go install ubunatic.com/uman@latest

See the demos View source Product home

Project snapshot · measured 2026-10-26

Key facts

Commits 179Last commit 2026-10-22 Source receipt ↗ Commits · 7 days 12 Source receipt ↗ Tickets closed 9 / 38 Source receipt ↗ Studies 2 Source receipt ↗

12-week commit activity

2026-10-26

Aug 3

Aug 10

Aug 17

Aug 24

Aug 31

Sep 7

Sep 14

Sep 21

Sep 28

Oct 5

Oct 12

Oct 19

View 12-week data table

Week starting	Commits
2026-08-03	8
2026-08-10	0
2026-08-17	1
2026-08-24	6
2026-08-31	5
2026-09-07	16
2026-09-14	6
2026-09-21	0
2026-09-28	2
2026-10-05	35
2026-10-12	1
2026-10-19	12

Key Features

One table shows projects with local changes and branches ahead of or behind their Git remotes.
Bulk push skips unsafe repositories; choose files for a coding agent to commit interactively.
Copies project sites into the publishing repository and offers a local preview server.
Scans sites for private addresses, local paths and credential-like text before publishing.

Verified Engineering Milestones

Detection of duplicate and mismatched Git remotes (#025, 84614bc)
Agent-assisted push with staged file selection (#027, #028, a92870d, 6676fe6)
Website scan blocks publishing when it finds sensitive data (#032, e1c11e6, dae0e4b)

Stack

Go 1.25.0, Cobra, TOML/YAML, Git, terminal UI, local HTTP serving

Why uman

One workspace, shared checks

A directory of independent Git repositories tends to accumulate one-off scripts for the same jobs: check status, run tests, validate licenses and publish project sites. Those scripts drift and their results are easy to miss. Uman applies these operations from a single project list and reports results together.

Recorded demos

Common workspace tasks

uman status

Review working-tree changes and remote divergence across the configured projects.

uman run

Run project commands concurrently and collect their results in one invocation.

uman reuse

Inspect and validate REUSE licensing metadata across the workspace.

uman website

Copy project website content and serve it locally for review.

Capabilities

Coordinate work without hiding repository state

Workspace status

See local changes, branches and ahead/behind counts across configured repositories.

Parallel commands

Run a command across projects concurrently and review each result.

Workspace doctor

Check project scaffolding and site setup for common drift and conflicts.

License checks

Initialize and lint REUSE metadata across projects.

Website tools

Sync project site files and serve a local preview before publishing.

Guarded Git operations

Review remote and working-tree state before pushing or selecting staged files.

Quickstart

Set up a workspace

Install uman, initialize its project list and use the same commands from that workspace.

uman init
uman status
uman doctor
uman run -j 4 -- git status

Engineering story

Shared workspace checks and guarded coordination

Read the workspace coordination story for the design of cross-repository status, staging and publishing workflows.

Project details

Stack

Go 1.25.0, Cobra, TOML/YAML, Git, terminal UI, local HTTP serving

Milestones

Detection of duplicate and mismatched Git remotes (#025, 84614bc) · Agent-assisted push with staged file selection (#027, #028, a92870d, 6676fe6) · Website scan blocks publishing when it finds sensitive data (#032, e1c11e6, dae0e4b)

Source

https://codeberg.org/ubunatic/uman ↗

Architecture

Layer composition

Terminal: CLI, TUI
Desktop: Linux
Inference / AI: coding agents for commit messages
Containers / VM: —
Web: website sync, local preview server

Engineering story

uman: the story behind the project

Most developers accumulate projects faster than they accumulate good ways to look after them. A workspace with dozens of independent Git repositories turns small chores into repeated work: checking which branches are ahead, deciding what is…

Read the engineering story

Measurement source · 2026-10-26

Verification receipts

Commits: 179 · Last commit 2026-10-22
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Commits · 7 days: 12
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Tickets closed: 9 / 38
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
Studies: 2
git -C <repo> rev-list --count HEAD; git -C <repo> rev-list --count --since=<ISO-week-Monday> --until=<ISO-week-Sunday> HEAD; git -C <repo> rev-list --count --since=<measured-date-6-days>T00:00:00 --until=<measured-date>T23:59:59 HEAD; git -C <repo> log -1 --format=%cs HEAD; ls <repo>/issues | grep '^[0-9].*\.md$'; grep -l -E '^\*\*Status\*\*: *(Closed|Done|Resolved|Fixed|Complete)' <repo>/issues/*.md | wc -l; ls <repo>/docs/studies/*.md
repositories behind spec project ids in ~/projects; private-repo filter is a safety net and matches no spec project today; missing repos reported separately; seven calendar days ending on measured date in the measuring host's local timezone; commit counts include all authors and merge commits reachable from HEAD · measured 2026-10-26
12-week commit activity
git rev-list --count --since=<Monday> --until=<Sunday> HEAD
12 latest complete ISO weeks; weekly values are from spec/metrics.yaml.