Move and tweak SKILLS, so they're found and used - #8131
Merged
Amaury Chamayou (achamayou) merged 5 commits intoAug 10, 2026
Conversation
Amaury Chamayou (achamayou)
approved these changes
Aug 7, 2026
Amaury Chamayou (achamayou)
enabled auto-merge (squash)
August 7, 2026 15:28
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adjusts the repository’s Copilot skill definitions and references so the existing “testing” and “formatting-and-linting” guidance is more likely to be discovered/used by agents (helping avoid wasted time running ctest directly instead of the project’s tests.sh wrapper).
Changes:
- Normalizes skill front matter (skill
namevalues now match directory names; updated descriptions). - Updates
.github/copilot-instructions.mdto link directly to the skill files. - Minor wording tweak in the formatting/linting skill text.
Custom instructions used:
.github/copilot-instructions.md
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
.github/skills/testing/SKILL.md |
Updates skill front matter (name/metadata) and clarifies when to use the testing guidance. |
.github/skills/formatting-and-linting/SKILL.md |
Updates skill front matter and minor wording tweak in instructions. |
.github/copilot-instructions.md |
Fixes pointers to the new skill file locations so agents can find the intended guidance. |
Suppressed comments (2)
.github/skills/testing/SKILL.md:4
user-invocableis introduced in the skill front matter, but this key is not referenced anywhere else in this repo (and the skill itself doesn't explain what it does). To avoid future confusion, either add a brief note/link to the spec that defines this field, or remove it if it's not required.
.github/skills/formatting-and-linting/SKILL.md:4user-invocableis added to the front matter, but it's not referenced anywhere else in this repository and isn't explained within the skill file. Consider documenting what it does (with a reference) or removing it if it's unnecessary, to keep the skill metadata self-explanatory.
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.
[Write a witty PR description outlining the following story:
ctest, seeing it fail, and wasting time debugging venv activation issues.tests.sh.Include some gifs from Taken ("I have a particular set of skills"), and the Matrix (Neo getting skills injected, "I know kung fu") for visual learners. Maybe include screenshots of the VSCode
/skillswindow before and after, to make it dead clear they were previously invisible but now auto-discovered. But I guess a cropped screenshot like that is beyond your abilities. Once upon a time I would have written this myself. Is this getting too meta?]