Turn .cursorrules / repo guidelines into GitHub pre-merge checks (OSS)
Semantic diff-to-issue alignment + agentic rule generation—solves real maintainer pain from Copilot volume.

Proves private work exists without exposing code or repo names.
Developers with private repos, freelance work, or multiple GitHub accounts
GitHub Contributions · ReadME · Credly
All my real work is in private repos under company accounts, client organizations, or separate work emails. I had no way to show that output to anyone without violating NDAs or sharing proprietary code. So I built Unified Contribution Portal (UCP). You connect your GitHub accounts via personal access tokens (read-only, contribution metadata only). UCP fetches dates and counts — no repo names, no commit messages, no code — and merges everything into a single 52-week heatmap. The token is used once and discarded. Nothing is stored. Live: https://unifiedcontributions.vercel.app/ It's free. I launched on Product Hunt today and have zero users. I'm trying to figure out if this is a real problem other developers have or just a problem I had. Honest questions for HN: 1. Do you have the same problem — work that's invisible on your public profile? 2. Would you use this? What's missing? 3. Is there something obviously broken with the approach? Happy to answer anything about how it works technically
Semantic diff-to-issue alignment + agentic rule generation—solves real maintainer pain from Copilot volume.
3D-printed GitHub graphs when gh-skyline already generates free STL files.
Clever satire flipping the contribution graph, but offers no actionable insights beyond status page data.
Three.js GitHub viz with audio, but another commit graph in a crowded field.
Turns your commit history into a 3D planet with generative audio soundtrack.
GitHub commit leaderboard; removes novelty once the initial curiosity wears off.