PortfolioOps
Local-first control centre for keeping an engineering portfolio honest and useful
what it proves
Proves operational product thinking: turning a growing set of repositories into a reviewable system with evidence-based hygiene scores, honest fallbacks and a clear next-action queue.
A private portfolio operations dashboard that scans the repositories GitHub exposes, checks README, documentation, tests, CI and Docker signals, and turns those findings into readiness scores and practical next actions. Public repositories can sync without credentials; private or unavailable repositories fall back to clearly labelled curated data rather than fabricated GitHub results.
proof points
- Scans GitHub-visible repositories and derives five consistent engineering-hygiene checks
- Labels private, offline and rate-limited fallbacks instead of presenting curated data as live GitHub evidence
- Ranks portfolio readiness and practical next actions from one local-first dashboard
- Keeps interview-preparation judgement separate from automatically scanned repository facts
skills demonstrated
tech stack
engineering hygiene
- ✓ readme
- ✓ docs
- ✓ tests
- ✗ ci
- ✗ docker
Known gaps: ci, docker. Next step: add CI so the existing scanner and registry tests run automatically on every change.
where to see it
The repo is currently private. The evidence on this page comes from the case study; happy to walk through the code in a conversation.