Skill to test changes using just-built MSBuild#13202
Conversation
A standard part of the inner developer loop in this repo is to build MSBuild with a change, then run it against a repro project or projects to validate that MSBuild is generally working and the change affects the behavior you expect. Adding a skill to (hopefully!) make that crystal clear to agents.
There was a problem hiding this comment.
Pull request overview
This PR adds a new skill document to guide developers through testing bug reproductions using the locally-built MSBuild (bootstrap). The skill provides step-by-step instructions for building MSBuild, running repro projects against the built version, and troubleshooting common issues.
Changes:
- Added
.github/skills/use-bootstrap-msbuild/SKILL.mdwith comprehensive guidance on using the bootstrap MSBuild for testing bug fixes
baronfel
left a comment
There was a problem hiding this comment.
Lovely to have! Will CCA use this automatically, or is there some kind of registration step that needs to happen so that agents see this?
|
Also, a nit - this won't work with Claude Code due to its location expectations. It would be ideal to have a way to easily reuse skill definitions across the major players. |
I looked at docs a bit and as far as I can tell there is an interoperable location but it's |
|
@rainersigwald just slap a symlink real quick - this is what Viktor and I did for his skills repo to lower the cost |
AFAIK it will be known to any Copilot invocation after this is checked in (the directory structure is the registration). I did It's not totally clear to me though how well things will pick up on and use it. I think we'll have to try it and see. |
A standard part of the inner developer loop in this repo is to build MSBuild with a change, then run it against a repro project or projects to validate that MSBuild is generally working and the change affects the behavior you expect. Adding a skill to (hopefully!) make that crystal clear to agents.
A standard part of the inner developer loop in this repo is to build MSBuild with a change, then run it against a repro project or projects to validate that MSBuild is generally working and the change affects the behavior you expect.
Adding a skill to (hopefully!) make that crystal clear to agents.