Looking for contributors: git-courer, an MCP layer that stops AI agents from running raw git

'm looking for people to help contribute to git-courer, an MCP server I've been building in Go. The roadmap is public, one issue per release, each with clear acceptance criteria — no vague "help wanted" labels with zero context. A few open right now:

• Removing dead fields from the data model — small, mostly compiler-guided cleanup, good if you want a first PR without learning the whole codebase.
• Adding a from flag to branch creation, so an agent can branch from any tag/commit instead of always forking from HEAD. Self-contained, no dependencies on the rest of the roadmap.
• Automatic PR attribution in changelogs after a pull, matching commits to PR numbers by branch name. The meatiest one — real design challenge if that's what you're after.
• A small one in the AST classifier so deleted files get their own commit type instead of being lumped into refactor:.

For context on why this exists: the core idea is that no AI agent should ever run raw git again. It parses the AST of every diff, classifies changes deterministically, and only hands a local LLM the job of writing the commit message — zero API tokens spent on the structural part. It's grown into 22 (soon 12, I'm mid-refactor on that one myself) MCP tools covering the full git lifecycle: structured JSON instead of text to parse, auto-backup before anything destructive, a pre-PR gate that runs tests and checks conflicts in one call.

It's picked up some organic traction (engineers from a few well-known companies starred it without me reaching out), but I want it to grow as a real collaborative project, not just my solo thing.

Repo: https://github.com/blak0p/git-courer

Built in Go, uses Ollama for the local LLM part. If you're into Go, MCP, or local-LLM tooling, I'd love the help — happy to answer anything about the architecture.