feat(eval): add lightweight skill contract checks - #4
Open
Scared-Heart 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.
Summary
This PR adds a first lightweight eval layer for the Skill repository. The goal is to protect important Skill instruction contracts from accidental Markdown regressions, not to introduce full model-based evals yet.
Changes included:
teambitionandteambition-statisticsfilterTqlrulesmainScope
This is intentionally a small v0. It only reads local Markdown and JSON files. It does not:
I think this still provides value as a baseline regression guard, because the current Skills are mostly instruction-driven and important behavior can regress through seemingly small Markdown edits.
Future direction
If this direction looks useful, the next layer could add mocked tool-call evals or optional integration-style evals against a test workspace. Those would be better suited for validating actual agent behavior, while this PR focuses on keeping the existing instruction contracts stable.
Verification
npm testResult: 2/2 eval cases passed.