What I do
- Look up the documentation for the
critCLI tool (https://github.com/tomasz-tomczyk/crit) to understand how to use it effectively. - Launch Crit for a plan file or the current git diff.
- Note: you must run
critin the background and leave it running for the duration of your session, otherwise you block the main conversation thread and the user cannot continue to interact with you.
- Note: you must run
- Wait for the user to review changes in the browser.
- Read
.crit.jsonand address unresolved inline comments. - Signal the next review round with
crit go <port>when edits are done.
Workflow
- Decide whether to review a specific file or the current git diff.
- Run
crit <file>for an explicit file, orcritfor git mode. - Tell the user to leave inline comments in the browser, click Finish Review, and reply with
gowhen they are done. - Read
.crit.jsonand find comments whereresolvedisfalse. - Revise the referenced files to address each unresolved comment.
- Mark comments resolved in
.crit.jsonif the workflow calls for it. - Run
crit go <port>to trigger the next review round.
Guardrails
- Do not continue past the review step until the user confirms they are done.
- Treat
.crit.jsonas the source of truth for line references and comment status. - If there are no unresolved comments, tell the user no changes were requested and stop.