$ loading_
Detects omitted co-changing files and C# members around your code edits.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "Unwritten" MCP server from askskill: Run: claude mcp add 'io-github-byggarepop-unwritten' -- npx -y Unwritten
After editing C# code, developers can use it to see which files or members historically changed together but were not updated this time, reducing missed changes. It is useful after refactors, interface updates, or logic moves.
Before commit or merge, teams can use it to check the current change set for potentially omitted related files and members. This helps catch incomplete updates before code reaches the main branch.
Reviewers can use it as a support tool to see whether the current change is missing historically common co-changes. It helps complement manual review where change relationships are hard to fully track.
It is a Git-history “hole” detector that flags files and C# members that tend to change together with your current edit but are absent this time. It is useful for spotting missed-change risks.
Based on the description, it works at both file level and C# member level. For support of other languages or more detail, see the source repository.
The provided material does not include installation steps, runtime requirements, or dependency details. See the source repository for prerequisites and setup.
Generate standardized Git commits from diffs with logical grouping support.
Analyze local Git changes not yet on GitHub for faster review and cleanup.
Automatically resolves Git merge conflicts so agents handle only complex hunks.
Run multi-model reviews for code changes, PRs, and risky edits.
Review Git diffs and Markdown with a web UI and MCP AI access.
Generate shareable code or text diffs for review and collaboration.