fix(skill): update skills - adding get_example for component example look up - #17489
Open
Marina-L-Stoyanova wants to merge 2 commits into
Open
fix(skill): update skills - adding get_example for component example look up#17489Marina-L-Stoyanova wants to merge 2 commits into
Marina-L-Stoyanova wants to merge 2 commits into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates multiple Ignite UI for Angular agent skill guides to prefer the new get_example Ignite UI CLI MCP tool for retrieving working code samples, while keeping get_doc as a fallback when narrative/explanatory context is needed.
Changes:
- Switched several “look up docs first” instructions from
get_doctoget_example, withget_docas an explicit fallback for explanation-heavy scenarios. - Updated CLI MCP guidance in the components/grids skills to describe when to use
get_examplevsget_doc(and recommending thelanguageparameter to reduce response size). - Updated image/figma workflow skills to require
get_examplebefore generating component code.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| skills/igniteui-angular-grids/SKILL.md | Updates required workflow and overview guidance to prefer get_example for grid-related code lookups. |
| skills/igniteui-angular-generate-from-image-design/SKILL.md | Updates pre-coding checklist and component lookup steps to use get_example first. |
| skills/igniteui-angular-figma-to-app/SKILL.md | Updates doc-fetching workflow to call get_example (with get_doc fallback); one internal consistency issue remains (comment added). |
| skills/igniteui-angular-components/SKILL.md | Updates Ignite UI CLI MCP server description and required workflow to prefer get_example for working code. |
Comment on lines
381
to
+385
|
|
||
| Call `list_components({ framework: "angular" })` **once** to discover which component | ||
| families have full docs — **the catalog covers only a subset of components**. Then: | ||
|
|
||
| - For families **with** a doc: call `get_doc({ framework: "angular", name: "<doc-name>" })`, | ||
| all in a single parallel batch — never sequentially. | ||
| - For families **with** a doc: call `get_example({ framework: "angular", name: "<doc-name>" })` (or `get_doc` when explanation context matters), all in a single parallel batch — never sequentially. |
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.
Motivation / Context
Updating the skill files to used the new get_example MCP tool
Type of Change (check all that apply):
Component(s) / Area(s) Affected:
How Has This Been Tested?
Test Configuration:
Screenshots / Recordings
Checklist:
feature/README.MDupdates for the feature docsREADME.MDCHANGELOG.MDupdates for newly added functionalityng updatemigrations for the breaking changes (migrations guidelines)