The Context Switching Tax
As developers, our flow is sacred. But every Friday, I had to stop coding to perform "translation work" for my clients. They didn't care about "Refactored the auth middleware," they wanted to know "The login system is now more stable."
The Solution
I built a pipeline that uses the GitHub API to fetch my activity and passes it through a structured prompt engine.
Key Technical Challenges I faced:
Context Mapping: I created a "Soul Map"—an initial index of the repo so the AI understands the project's domain before reading a single commit.
Deep Code Analysis: Implementing a way to read diffs securely in-memory without persisting any source code.
I turned this into a tool called commitplain. I’m curious: how do you guys keep your non-technical stakeholders in the loop without losing your mind?
Check it out here: https://commitplain.com
Top comments (0)