[TypeSpec Authoring][PoC] Agentic search only approach #16267
Draft
haolingdong-msft wants to merge 9 commits into
Draft
[TypeSpec Authoring][PoC] Agentic search only approach #16267haolingdong-msft wants to merge 9 commits into
haolingdong-msft wants to merge 9 commits into
Conversation
Squashed net changes of typespec-authoring-agentic-search-only vs main: - azure-typespec-author SKILL.md + references (agentic search only; drop authoring-plan MCP tool) - evaluate/ eval cases and consolidated forced/no-skill/trigger suites - fixtures: Widget package.json/package-lock.json; gitignore result/ Co-authored-by: JoyerJin <joyerjin@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…entic-search-only-clean # Conflicts: # .github/skills/azure-typespec-author/evaluate/evals/002002.eval.yaml # .github/skills/azure-typespec-author/evaluate/evals/003001.eval.yaml # .github/skills/azure-typespec-author/evaluate/evals/003002.eval.yaml # .github/skills/azure-typespec-author/evaluate/evals/005001.eval.yaml # .github/skills/azure-typespec-author/evaluate/suites/forced.eval.yaml # .github/skills/azure-typespec-author/evaluate/suites/no-skill.eval.yaml # .github/skills/azure-typespec-author/references/validation.md
…RL, add 002011 eval coverage - Remove ARM versioning URL (https://azure.github.io/typespec-azure/docs/howtos/arm/versioning/) which now redirects to the already-listed evolving-apis page - Update doc-coverage.md with new eval 002011 (checkExistence HEAD op) mapped to Case 2 — Add Resource Operations (ARM) - All 8 case headings present and non-empty - All URLs verified HTTP 200 - 0 eval cases with missing related docs Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add 4 new authoritative URLs across existing cases: - Case 2: ARM step 04 (custom actions walkthrough) - Case 3: Uncommon scenario for converting specs with multiple previews - Case 6: TypeSpec core scalars reference - Case 7: Azure Core decorators reference Fix Case 2 step 05 link text (was mislabeled as 'Custom Actions', now correctly says 'long-running resource operations'). All 51 URLs verified to return HTTP 200. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
📊 GEPA Skill Quality Scores
9/11 skills at quality ≥ 0.80 How to improve# Score a specific skill
python .github/skills/sensei/scripts/gepa/auto_evaluator.py score --skill <name> --skills-dir .github/skills --tests-dir tests
# Optimize a skill with GEPA
python .github/skills/sensei/scripts/gepa/auto_evaluator.py optimize --skill <name> --skills-dir .github/skills --tests-dir tests |
…entic-search-only-clean # Conflicts: # .github/skills/azure-typespec-author/evaluate/suites/forced.eval.yaml # .github/skills/azure-typespec-author/evaluate/suites/trigger.eval.yaml
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.
Fix #15676