- Sphinx is introduced as a tool that steps in just before a developer pushes code to a remote repository and asks what the changes made by an AI coding tool actually do. A Git hook refers to such an automatic execution point.
- The original example is a situation where an event ID is saved before a charge() call while processing a payment webhook. It raises the question that a customer may not be charged when a retry follows a failed payment. This is an illustrative example and not an actual usage record.
- The original states that the questions are written by a separate reviewer that has never seen the user's conversation history, reading the diff, meaning the difference in changed code. If the answer is wrong, it asks again with a different scenario. If the answer is right, the push continues.
- According to the original, it can be set to stop only on protected branches, the check can be skipped with the sphinx yolo command, and skipped runs are recorded. The answers are not passed to the coding agent, and .env files and keys are not opened.
- The original says it works with Codex, Claude Code, Cursor, OpenCode, Pi, and plain Git. Installation requires Node 22.19 or later and macOS, Linux, or WSL. The claim that it was built to work with minimal tokens is the makers' design claim.
O: For developers who often change code like payment webhooks with AI coding tools, it can be useful right before a push: Sphinx asks questions, and you check your own change by explaining in your own words what happens when it fails.
X: The sample conversation in the original is only illustrative, and it gives no measurement of question accuracy or how often false warnings occur, so you need to think through how often a wrong answer would block a push.