01Requests
Gather scattered intent, one line each
Pulls requirements out of what you asked your coding AI, your test code and your own answers, one per row.
DevHive reads your intent from what you asked your coding AI and from your tests, then checks every commit you push against it.
Where the intent falls short, it asks first instead of filling it in.
Open to invited teams first
From collecting your requests to asking about missing intent, DevHive follows each commit and takes on the work along the way.
01Requests
Pulls requirements out of what you asked your coding AI, your test code and your own answers, one per row.
02Commit check
Row by row, it marks whether the changed code in a pushed commit keeps the requirement, keeps it only if assumed, differs from it, has no code for it, or can't be told.
03Flow
Shows what each changed function calls as boxes and arrows, and fills in how an example value flows at each step.
04Code map
Links function calls from syntax alone, with no model call. The code behind each verdict, the tests that reach it and what spills outside the request all come from this map. Click a function to see its neighbors.
05Assumptions
When the AI decided something the request never said, it's marked 'Only if assumed'. If it's right, confirm it as an answer; if not, send a fix request.
06Questions
What the request doesn't say is asked, not filled in. Your answer goes into the intent and the commit is checked again.
07Fix request
See a Differs or an Unknown, send a fix request, and your coding AI picks it up and fixes it. Push the new commit and it's checked again.
Questions that go back to the developer look like this
Connect DevHive to the coding AI you use and ask as you always do. When you push, DevHive takes the commit, checks it against your intent and, if there's something to look at, puts it in Needs attention.
MCP and a hook keep the request text
Each requirement row quotes its source
Marked as asked, only if assumed, differs, no code or unknown
Your answer goes into the intent and the commit is checked again
Connect over MCP and your coding AI keeps your request text and answers DevHive's questions.
One per person
https://getdevhive.com/mcpAdds .mcp.json and the request hook to your repository. Open it from the repository's top folder.
Add it once to your global settings and approve the hook.
Split the work by role, and every action is on record.
08Projects
Reads only the repositories you allow in the GitHub app.
09Roles
Only admins change settings and members.
10Activity
Requests, commits, checks and questions, in order.
11Korean · English
The app screens and the questions come in Korean and English.
DevHive doesn't judge whether your request is right.It only checks the code against the requests and tests as written.
No. It only reads the repositories you pick. It doesn't install or build anything.
Yes. To check a commit it sends the changed files, the request text and parts of the tests to an AI model. You choose which repositories it can read when you install the GitHub app.
Claude Code and Codex. They connect over MCP, and a hook sends the request text. The Connect your coding AI screen writes the setup files.
When you connect a repository, it builds a map of its function calls first. TypeScript and JavaScript are read down to individual functions. Other languages are read file by file.
DevHive doesn't judge whether your intent is right. It only checks the code against the intent as written, and what it couldn't read stays Unknown.
No. People approve and merge on GitHub. DevHive only checks commits and asks.
It can leave commit check results on GitHub. It doesn't write PR comments or reviews.
Reading code and commits, proposing the connection setup as a PR, and leaving commit check results on GitHub.