You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+37Lines changed: 37 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -319,6 +319,43 @@ When reviewing documentation, do the following:
319
319
- Read the documentation on the wiki located in [this git repository](https://github.com/microsoft/DirectXTK.wiki.git).
320
320
- Report any specific gaps in the documentation compared to the public interface.
321
321
322
+
## Code Change Rules
323
+
324
+
- Make precise, surgical changes that **fully** address the request. Don't modify unrelated code, but ensure changes are complete and correct.
325
+
- Don't fix pre-existing issues unrelated to your task. However, if you discover bugs directly caused by or tightly coupled to the code you're changing, fix those too.
326
+
- Update documentation if it is directly related to the changes you are making.
327
+
- Always validate that your changes don't break existing behavior.
328
+
329
+
### Linting, Building, Testing
330
+
331
+
- Only run linters, builds and tests that already exist. Do not add new linting, building or testing tools unless necessary for the task.
332
+
- Use the smallest targeted test, build, or lint command that covers the changed behavior. When related targeted selectors use the same runner, include them in one invocation; escalate to full-suite or baseline runs only when targeted validation shows they are needed.
333
+
- Documentation changes do not need to be linted, built or tested unless there are specific tests for documentation.
- Install packages only when changing dependencies or after a missing-dependency failure.
339
+
340
+
### Code Commenting Style
341
+
342
+
- Only comment code that needs a bit of clarification. Do not comment otherwise.
343
+
322
344
## Release Process
323
345
324
346
The release process is documented in the [release skill](.github/skills/release/SKILL.md). Invoke the `release` skill for step-by-step guidance when performing a release.
347
+
348
+
## CoPilot Skills
349
+
350
+
The project includes published CoPilot skills for developers:
351
+
352
+
-**Release-Process**: Guide for performing the DirectX Tool Kit release process. Invoked when asked to help with releasing a new version, publishing packages, or updating ports. See [Release Process skill](.github/skills/release/SKILL.md) for details.
353
+
-**directxtk-usage**: Provides usage guidance for the DirectX Tool Kit for DX11 library. Located in the `skills/directxtk-usage/` directory.
354
+
-**directxtk-tutorial**: Provides an interactive tutorial which can create a project, add the toolkit, and implement features in a step-by-step fashion. Located in the `skills/directxtk-tutorial` directory.
0 commit comments