Add twoperson to Development Tools - #117
Open
ahm3dwasim wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds twoperson to Development Tools.
twoperson enforces a two-person rule between two coding agents: a builder publishes a review packet and a reviewer records a verdict. The packet schema won't represent "pushed without a review reference" or "approved without a commit sha", so an approval is bound to one exact commit and goes stale on rebase. It maps cleanly onto a Codex-CLI reviewer leg (builder in one agent, Codex reviewing), ships a Stop-hook installer so the reviewer wakes on session end, scans packets for credentials, and is git-worktree aware. Pure Python, MIT, on PyPI.
Appended to the end of the section per the list's order.