Add agent dev skill for search#45972
Merged
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a package-specific “agent dev skill” for azure-search-documents to guide post-TypeSpec-regeneration validation and re-application of hand-authored _patch.py customizations, and registers it in the repo-wide package skill registry.
Changes:
- Added a
search-documentsskill (SKILL.md) describing regeneration verification steps and customization patterns. - Added a
references/customizations.mdinventory of_patch.pycustomizations and their generated-code dependencies. - Updated the central
find-package-skillregistry to includeazure-search-documents.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
sdk/search/azure-search-documents/.github/skills/search-documents/references/customizations.md |
New checklist documenting each customization file’s defined symbols and regeneration verification points. |
sdk/search/azure-search-documents/.github/skills/search-documents/SKILL.md |
New skill guide for post-tsp-client update regeneration verification and customization re-checks. |
.github/skills/find-package-skill/SKILL.md |
Registers the azure-search-documents package skill in the central skill lookup table. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
laiapat
reviewed
Mar 28, 2026
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Mar 31, 2026
Add the find-package-skill discovery skill at .github/skills/, matching the pattern established in azure-sdk-for-js, azure-sdk-for-python, and azure-sdk-for-net. This skill serves as a routing table that tells AI agents to check for package-specific domain knowledge before modifying any SDK package. The package skills table is currently empty — package teams can register their skills here as they create them (e.g., azure-search-documents). Related PRs: - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
maorleger
added a commit
to Azure/azure-sdk-for-net
that referenced
this pull request
Mar 31, 2026
) ## What This PR adds support for **package-specific skills** — tribal knowledge that agents load before modifying SDK packages. Two files: 1. **`.github/skills/find-package-skill/SKILL.md`** — a discovery skill that teaches agents how to find package-specific skills by checking for `.github/skills/` inside the package directory they're modifying. No hardcoded lookup table — the directory structure IS the source of truth. 2. **`sdk/search/Azure.Search.Documents/.github/skills/search-documents/SKILL.md`** — placeholder skill for Search with scaffolded sections for domain experts to fill in. ## Related PRs - Azure/azure-sdk-for-js#37484 - Azure/azure-sdk-for-python#45972 ## Callouts - @efrainretana is working on the contents of the Search skill for dotnet — this placeholder provides the hook for it to be picked up correctly. - Other language repos (JS, Python) currently use a registry table approach. If directory inference works well here, we could bring it to those repos too.
laiapat
reviewed
Apr 1, 2026
…nts/references/customizations.md Co-authored-by: McCoy Patiño <39780829+mccoyp@users.noreply.github.com>
laiapat
reviewed
Apr 10, 2026
hizixin
approved these changes
Apr 14, 2026
Member
|
I also have a skill for this package in my branch that covers the end-to-end release workflow (phases 0–7: regen, sync patch files, tests, lint, changelog, samples, versioning). I'll send a follow-up PR after this merges to integrate the two. |
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint + anchor checker) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ### 4. validate_skill_anchors.py (staleness checker) Extracts code references from skill markdown and verifies they still exist in the codebase. Catches renamed methods, deleted files, cross-language pollution. Tested: 22/22 anchors pass for search skill. ## Key design decisions - Skill name = Maven artifactId (azure-search-documents, not search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 - Gist: https://gist.github.com/samvaity/4981de850ce51a29fdeb7a7d063ebddc Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
2 tasks
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 16, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 17, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 17, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
samvaity
added a commit
to samvaity/azure-sdk-for-java
that referenced
this pull request
Apr 17, 2026
Adds the infrastructure for service teams to create, validate, and maintain package-specific Copilot skills -- the tribal knowledge that helps AI agents work correctly on their SDK packages. ## What's included ### 1. find-package-skill (discovery registry) Routes agents to package-specific skills before modifying any SDK package. Matches the pattern from JS, Python, and .NET repos. ### 2. create-package-skill (bootstrap wizard) Interactive wizard that walks service teams through creating a skill: - Phase 0: Scan package (detect architecture, customizations, key files) - Phase 1: Scaffold SKILL.md (common pitfalls, error categorization, patterns) - Phase 2: Generate references (architecture.md, customizations.md) - Phase 3: Validate (vally lint) - Phase 4: Register in find-package-skill table ### 3. azure-search-documents (first package skill) Created using the wizard as a dogfood. Covers: - Error categorization table (generated/@generated vs hand-written) - SearchCustomizations.java fragility patterns - ServiceVersion dedup guards - Breaking change detection - Clear MCP tool handoff (activates after generate-sdk-locally shared skill) ## Key design decisions - Skill name = Maven artifactId (azure-search-documents) - No version numbers in skills -- keep content static - TypeSpec-first customization guardrail - Skills activate after MCP tools have been tried -- no duplication - Based on eval data: 1/3 -> 4/4 correct fix locations with skill ## Related - JS: Azure/azure-sdk-for-js#37484 - Python: Azure/azure-sdk-for-python#45972 - .NET: Azure/azure-sdk-for-net#57580 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
fafhrd91
pushed a commit
to fafhrd91/azure-sdk-for-python
that referenced
this pull request
Apr 28, 2026
* Add agent dev skill for search * Update .github/skills/find-package-skill/SKILL.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> * update * Update sdk/search/azure-search-documents/.github/skills/search-documents/references/customizations.md Co-authored-by: McCoy Patiño <39780829+mccoyp@users.noreply.github.com> * updates * shorten the description * updates * clean up for 12.0.0 --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: McCoy Patiño <39780829+mccoyp@users.noreply.github.com>
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.
Description
Add an agent dev skill for the search-documents package
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines