Verified Solution

[microsoft/vscode] Copilot bypasses rename tool in VS Code 1.110 despite explicit SKILL.md guidance

Sponsored Content
### ROOT CAUSE The issue arises because the Copilot extension isn't adhering to the `symbol-rename` skill's mandatory rule in the `SKILL.md` file, which specifies the use of `vscode_renameSymbol`. This could be due to a misconfiguration in the skill's directives or a bug in how Copilot processes rename operations. ### CODE FIX 1. **Ensure Correct SKILL.md Configuration**: - Verify that the `symbol-rename` skill in `SKILL.md` is correctly formatted, especially the mandatory rules. Ensure there are no typos or formatting issues that might cause Copilot to ignore the rules. 2. **Update Copilot Extension Settings**: - Modify Copilot's settings to prioritize the `symbol-rename` skill when handling rename requests. This can be done by adding configurations that enforce the use of `vscode_renameSymbol`. 3. **Implement Skill Enforcement**: - If necessary, adjust the Copilot extension's code to ensure that it checks the `SKILL.md` file and enforces the specified rename method before falling back to other techniques. Here is a potential code snippet to modify the Copilot settings to prioritize the `symbol-rename` skill: ```json // settings.json { "copilotChat.enabled": true, "copilotChat.agentSettings": { "skills": { "priority": ["symbol-rename"] } } } ``` This change ensures that the `symbol-rename` skill is checked first, promoting the use of `vscode_renameSymbol` as intended.
Deploy on DigitalOcean ($200 Credit)

Related Fixes

[StackOverflow/docker] Cannot get npm installed app to be present in final Docker image
[microsoft/vscode] All of a sudden the whole VS code extensions got refreshed on their own.
[microsoft/vscode] [9699:0626/093542.027629:VERBOSE1:key_storage_util_linux.cc(54)] Password storage detected desktop environment: GNOME [9699:0626/093542.027660:VERBOSE1:key_storage_linux.cc(122)] Selected backend for OSCrypt: GNOME_LIBSECRET