Skip to content
Mission Ascent · Pre-launch
T–00:00:10
Loading assets0%
Mohit Agarwal
1st · Craft Winter Challenge 2025

GitCraft

Connect a GitHub repo and get documentation that keeps itself up to date: specs, decision records and release notes, written into Craft.

When
Dec 2025
Crew
Solo
Domain
AI · Web
Stack
Node · Express · Next.js · MCP · Claude / Gemini · GitHub webhooks
GC-02 · Live feedRec
GitCraft screenshot
1st
Craft Winter Challenge
38
Commits
Live
Still maintained

The problem

Docs go stale the week after they're written. Nobody updates the architecture page when they merge a PR.

What I built

GitCraft listens to a repo through GitHub webhooks, reads what changed with an LLM, and writes the result into Craft over MCP: specs, architecture decision records and release notes. Sign-in is GitHub OAuth and it runs on Render and Vercel.

The hard part

Rewriting docs on every commit buried readers in noise. I added a check that skips trivial commits, grades the rest as major, minor or patch, and only writes release notes for major changes.

Models also kept returning JSON that was almost valid, which broke the pipeline. I added a recovery path in three steps so a bad response degrades gracefully instead of failing the run.

Result

First place in the Craft Winter Challenge 2025. I still maintain it.

Gallery · 1

01Landing page and GitHub onboarding.