I have a few questions that I need to consult

[seho-dev]

• If I have completed the review of some files and checked the box, in most scenarios I would expect that checking the box would execute git add xxx, and it would be even better if there were a unified commit entry point (and even a commit message could be generated); now my question is, author, what is your own workflow when using this software? After reviewing, do you copy the path and manually commit?

• Are there plans to add support for opencode, or to customize the host and key functionality for AI?

• Author, do you primarily develop software on Windows or macOS?

I originally wanted to develop similar software, but after I finished collecting all the information, I found that such software already existed. Therefore, I will do my best to improve it, because I believe this software is a necessity for the vast majority of people. And I salute you! 🫡

[jamesaphoenix]

Hi @seho-dev, apologies about the late reply.

The way I use this software is the following:

1. Do a ton of work in Claude/Codex
2. Move to a git worktree, load up Diffcore
3. Read through all of the groups sequentially to understand/absorb the code -> add comments for what the coding agent has missed
4. For any things that could have been prevented migrate these to promote based on the following:

• Lint rules first
• Types
• Tests (integration first)
• pgTap (db second)

I've found that I purely use this tool for visualisation and digesting PR's + providing feedback.

The reason I built this was I so tired of reading 100+ file diffs where nothing was grouped, Github PRs don't help.

Ideas:

• Are there plans to add support for opencode, or to customize the host and key functionality for AI? - Happy to support opencode raise a PR
• I normally develop on MacOSX

[jamesaphoenix]

@seho-dev any chance you can get an opencode PR up for us?