Original Summary

We write a lot of our code with Claude Code now, and reviewing it showed us a gap. The diff shows what changed. It won't tell you if the agent dropped a local database halfway through, loosened a test assertion it couldn't make pass, or edited a file after the last test run and never ran the tests again. The agent's summary at the end usually doesn't mention those either. So we built ISY. A CLI hooks into Claude Code, Codex CLI and Kimi and uploads the session transcript when the session ends and again when you push. A GitHub App matches the session to the pull request by commit SHA and leaves one comment there, updated in place. The comment is six lines at most and only covers what's new since the last session. Drafts stay quiet until they're ready for review. The model suggests findings, but plain code decides what gets published, and a finding that doesn't point to a real step in the session is dropped. Before upload, the CLI swaps API keys, database URLs and absolute paths for placeholders on your machine. The transcript on your disk is never touched. To set it up, install the GitHub App on a repo and run npm install -g nightloom/isy && isy init. The CLI is open source: github.com/nightloom-dev/ISY-cli It's in open beta at iseeyaai.com , and the free plan covers one repo and 10 PRs a month. If you review agent-written code, what has the diff hidden from you that you only found later?   submitted by   /u/Last_Response2754 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/10 01:50:31