feat(skills): contribute CA containerization skills gated behind aksskillsEnabledPreview

[benjaminbob21]

Bundle the five Containerization Assist skills (analyze-repo, generate-dockerfile, fix-dockerfile, generate-k8s-manifests, deploy-to-aks) from the containerization-assist-mcp package into dist/skills at build time and register them via contributes.chatSkills, each gated by a new aks.skillsEnabledPreview preview flag (default off). Coexists with the in-repo kickstart-* skills; the containerization-assist-mcp dependency is already present on this branch.

[Copilot]

Pull request overview

This PR adds support for contributing the Containerization Assist skill set to the extension by bundling skill prompt files into dist/skills at build time and registering them under contributes.chatSkills, gated behind a new preview setting (aks.skillsEnabledPreview, default off). It extends the existing Copilot agent/skill contributions without interfering with the in-repo kickstart-* skills.

Changes:

• Add a webpack build step to copy containerization-assist-mcp skills into dist/skills (and clean that directory on builds).
• Introduce aks.skillsEnabledPreview setting and conditionally contribute 5 new chat skills from ./dist/skills/**.
• Pin VS Code integration tests to run against VS Code 1.128.1.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
webpack.config.js	Cleans and copies Containerization Assist skill files into the webpack output (dist/skills).
src/tests/runTests.ts	Pins the VS Code version used by @vscode/test-electron integration tests.
package.json	Adds the preview flag and registers the 5 new chat skills pointing at ./dist/skills/....

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

[Tatsinnit]

Hi @benjaminbob21, great work on the build setup and script extraction!

I'd like to suggest consolidating aks.kickstartEnabledPreview and aks.skillsEnabledPreview into a single flag in this PR, rather than waiting for a future refactor. Here's the reasoning:

Why now is better than later:

• Both flags control access to the same conceptual feature: AKS agent/skill capabilities
• You're already planning to consolidate them when CA skills replace kickstart skills
• Consolidating now avoids a multi-phase refactor + deprecation cycle later
• Users see one clear setting for "enable AKS preview skills"
• Implementation: Keep aks.skillsEnabledPreview (or rename to aks.agentSkillsEnabledPreview for clarity), and update all kickstart skill when clauses to use it. ~15 lines of change in this PR.

Benefits:

• No future flag rename/migration needed
• Clearer semantics in settings UI
• Single source of truth for preview features
• Reduced maintenance burden when skills eventually merge

Would you be open to this in this PR? Happy to discuss if you see constraints I'm missing!

Also, let's also document if the previous flag is not documented properly. Thank you!

[bosesuneha]

@benjaminbob21 I feel we can have the skills available by default without having them gated behind a flag. As @Tatsinnit pointed out it might get confusing to maintain so many similar flags. For better clarity, could you please add the motivation behind adding the skills in the extension?

[benjaminbob21]

Hi @benjaminbob21, great work on the build setup and script extraction!

I'd like to suggest consolidating aks.kickstartEnabledPreview and aks.skillsEnabledPreview into a single flag in this PR, rather than waiting for a future refactor. Here's the reasoning:

Why now is better than later:

• Both flags control access to the same conceptual feature: AKS agent/skill capabilities
• You're already planning to consolidate them when CA skills replace kickstart skills
• Consolidating now avoids a multi-phase refactor + deprecation cycle later
• Users see one clear setting for "enable AKS preview skills"
• Implementation: Keep aks.skillsEnabledPreview (or rename to aks.agentSkillsEnabledPreview for clarity), and update all kickstart skill when clauses to use it. ~15 lines of change in this PR.

Benefits:

• No future flag rename/migration needed
• Clearer semantics in settings UI
• Single source of truth for preview features
• Reduced maintenance burden when skills eventually merge

Would you be open to this in this PR? Happy to discuss if you see constraints I'm missing!

Also, let's also document if the previous flag is not documented properly. Thank you!

Thanks Tats! Sounds great to me. Happy to make the change. Just some quick things to highlight, the current kickstart flag not only enables the skills but also the kickstart agent itself so might not totally be accurate to have it named aks.skillsEnabledPreview or anything with a skills naming. I expect that the kickstart agent shouldn't be enabled without the kickstart skills so they can't be under separate flags. I'm leaning towards Suneha's idea to just have the skills available by default without having them gated behind a flag.
Another option will be to just have the 5 skills gated behind the kickstartEnabledPreview flag or maybe some name more nuanced than that to accomodate all. Glad to have some more of your thoughts on this via teams chat for better conversations and get @bosesuneha opinions on this too.