Add RepoTrials to eval frameworks and harnesses - #78
Open
PozziTiv4ik 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.
What changed
Adds RepoTrials to §5a · Eval frameworks & harnesses (code-first test-runners).
Why it belongs
RepoTrials is an Apache-2.0, local-first Python CLI for building repository-specific coding-agent evaluations from real fixes already present in Git history. It reconstructs the pre-fix state, seals task material, validates BASE/RED/GOLD test transitions, runs repeated agent trials, and grades behavior with hidden tests rather than gold-diff similarity. It can also export tasks for Harbor.
The specific gap it addresses is task creation for a team's own repository: instead of relying only on a fixed public corpus or requiring every task to be authored by hand, it turns reviewed historical fixes into reproducible private evaluations.
Disclosure and maturity
I am submitting this on behalf of the project's maintainer and owner, @PozziTiv4ik. Version v0.1.0 is the first public release. The repository has a working demo and automated tests, but I am not claiming independent adoption or production maturity.
Validation
README.md, with one added entry.git diff --checkpasses.