-
Notifications
You must be signed in to change notification settings - Fork 154
feature/evals dod #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature/evals dod #173
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,16 @@ | ||||||||||
| { | ||||||||||
| "skill_name": "definition-of-done", | ||||||||||
| "evals": [ | ||||||||||
| { | ||||||||||
| "id": 1, | ||||||||||
| "prompt": "Modify lib/src/levenshtein.dart to add a comment explaining how the algorithm calculates distance (e.g. tracking deletion, insertion, substitution cost), and make sure you finish the task completely.", | ||||||||||
| "expected_output": "The file lib/src/levenshtein.dart has a new explanatory comment, code is formatted, analyzed cleanly, and contains no forbidden temporal terms.", | ||||||||||
|
Comment on lines
+6
to
+7
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If the agent is executed from the repository root, the path
Suggested change
|
||||||||||
| "expectations": [ | ||||||||||
| "The levenshtein.dart file contains a new comment explaining how edit distance is calculated.", | ||||||||||
| "The new comment does not contain any relative temporal words such as 'now', 'currently', 'new', 'old', or 'existing'.", | ||||||||||
| "The levenshtein.dart file is formatted cleanly according to dart format.", | ||||||||||
| "The project has no dart analyze errors or warnings." | ||||||||||
| ] | ||||||||||
| } | ||||||||||
| ] | ||||||||||
| } | ||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,10 @@ | ||
| { | ||
| "skills": {} | ||
| "skills": { | ||
| "definition-of-done-workspace": [ | ||
| { | ||
| "rule_id": "path-does-not-exist", | ||
| "file_name": ".agents/skills/definition-of-done-workspace" | ||
| } | ||
| ] | ||
| } | ||
|
Comment on lines
+2
to
+9
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Adding each individual workspace directory (like Instead of keeping the workspace directories inside This approach:
"skills": {} |
||
| } | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| registry=https://registry.npmjs.org/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In Git, if a parent directory is ignored (e.g., third-party skill folders), Git will not traverse into it, meaning sub-patterns like
!**/evals/will have no effect on them. Conversely, for un-ignored skill folders (likedefinition-of-done/), all of their contents are already un-ignored by default.Therefore, these rules are redundant and do not change Git's tracking behavior. If the goal is to track
evalsfor all skills (including third-party ones), you would need to un-ignore the parent directories first and then ignore everything else inside them exceptevals/.