-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Add find-package-skill registry for package-specific skills #48657
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
Changes from all commits
cdaa41d
47b0e27
3de677d
4763978
21bdc9e
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,25 @@ | ||
| --- | ||
| name: find-package-skill | ||
| description: '**UTILITY SKILL** — Must be consulted before making any changes to packages under sdk/. Provides package-specific domain knowledge that prevents common mistakes. WHEN: add feature to package; fix bug in package; modify package code; regenerate from typespec; change client library.' | ||
| --- | ||
|
|
||
| # Find Package Skill | ||
|
|
||
| Before modifying any SDK package in this monorepo, check this registry to see | ||
| if a package-specific skill exists. Package skills contain tribal knowledge | ||
| (architecture, data flows, type mappings, pitfalls) that prevents common mistakes. | ||
|
|
||
| Always check this registry before modifying any SDK package — even if you think | ||
| you already know the package well. | ||
|
|
||
| ## How to Use | ||
|
|
||
| 1. Find the package you're modifying in the table below. | ||
| 2. Read the SKILL.md at the listed path using the Read tool. Then read all files under the `references/` directory next to it for additional context. | ||
| 3. If the package isn't listed, no package-specific skill exists yet — proceed normally. | ||
|
|
||
| ## Package Skills | ||
|
|
||
| | Package | Path | | ||
| | -------------------------- | ------------------------------------------------------------------------------------------------- | | ||
| | `azure-search-documents` | `sdk/search/azure-search-documents/.github/skills/search-documents/SKILL.md` | | ||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,65 @@ | ||||||
| --- | ||||||
| name: search-documents | ||||||
|
||||||
| name: search-documents | |
| name: azure-search-documents |
Copilot
AI
Apr 14, 2026
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.
Same table formatting issue here: the extra leading pipe (||) will introduce an empty first column and mis-render the intended 2-column table. Use a single leading pipe (|) for each row/separator.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| # azure-search-documents SDK Architecture | ||
|
|
||
| <!-- TODO: Document the full source layout, generated vs custom split, | ||
| package map, service version rules, and dependency information. --> |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,4 @@ | ||
| # azure-search-documents — Customization Guide | ||
|
|
||
| <!-- TODO: Document JavaParser AST patterns, SearchCustomizations.java methods, | ||
| per-customization update guidance, and common customization patterns. --> |
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.
The markdown table has an extra leading pipe per row (
|| ...), which renders as an unintended empty first column on GitHub. Use a single leading pipe (| ...) for proper two-column table rendering.