Add unit-testing agents & skill - #4
Closed
JanKrivanek wants to merge 1 commit into
Closed
Conversation
Member
Author
|
This is not dotnet specific - so closing |
This was referenced Jun 3, 2026
leslierichardson95
added a commit
to leslierichardson95/skills
that referenced
this pull request
Jun 22, 2026
…+ compare opt-in Three changes from a dogfood-driven review: 1. Compare mode -> opt-in (step 2 dotnet#4 + step 6). Largest scaffold for least-common surface; users opt in if they actually need matrix.json side-by-side. Scaffold step now only emits Compare/* on opt-in. 2. Step 11 chat output restructured to lead with Quality as the headline evaluation. NLP framed as the zero-config sanity check (still on by default so first \dotnet test\ produces a real report). Safety + Compare listed as additional categories below. Step 2 tier table re-ordered with Quality on top and a 'Default' column for clarity. 3. New common-pitfalls section 'Tuning Quality for stylistic agents' covering the case where ELI5 / summarizer / strict-format / persona agents get punished by generic rubrics in CompletenessEvaluator and EquivalenceEvaluator. Includes three remediation patterns: - drop offending evaluators per app - rewrite goldens in agent voice - custom rubric-driven evaluator evaluators-catalog.md now has the full RubricEvaluator template (reads Quality/rubric.md, judges via the active IChatClient, emits a RubricFit numeric metric with rationale). Step 11 surfaces this caveat on first scaffold so users don't see bad Quality scores against a bad-fit rubric and conclude their agent is broken. eval.yaml adds three smoke assertions: - compare-mode-is-opt-in-not-default - pitfalls-doc-warns-stylistic-agents-fail-completeness Validator green (9 skills + 1 agent + 1 plugin). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
moesac0970
pushed a commit
to moesac0970/skills
that referenced
this pull request
Jul 4, 2026
…erop in Workforce API
Evangelink
added a commit
that referenced
this pull request
Jul 29, 2026
Failing check #4 validates the declared file rate against the summary attributes for both lines and branches, but the docstring listed only `line-rate`. This PR's own fixture fix corrected exactly a branch-rate mismatch (declared 0.60 against a 7/16 payload), so the omission hid a case the gate really does fail on. The README already documented both. Raised by review on the previous commit. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 57b65d53-dc7a-4d0a-b5c6-d17687018f01
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
1 participant
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.
Background
Prompt based version of code testing that works via couple agents cooperation (it's bit limited due to current limitation of nesting of subagent calls to just 1 level).
It is intentionaly not .net specific, but rather polygot solution
Open question