Add comprehensive guidelines for custom instruction files, localizati…#2
Merged
Add comprehensive guidelines for custom instruction files, localizati…#2
Conversation
…on, markdown standards, PowerShell Pester testing, and cmdlet development best practices - Introduced a new instruction file for creating high-quality custom instruction files for GitHub Copilot. - Added guidelines for localizing markdown documents, including directory structure and disclaimers. - Established documentation and content creation standards for markdown files. - Created a detailed guide for PowerShell Pester v5 testing best practices. - Developed PowerShell cmdlet and scripting best practices based on Microsoft guidelines. - Included guidelines for creating effective prompt files for GitHub Copilot.
There was a problem hiding this comment.
Pull Request Overview
This PR introduces comprehensive guidelines for custom instruction files, localization, markdown standards, PowerShell Pester testing, and cmdlet development best practices to guide GitHub Copilot in generating consistent, high-quality code across the repository.
Key Changes:
- Established standardized instruction file formats with required frontmatter and structured content
- Added PowerShell development standards covering cmdlet patterns, error handling, and pipeline support
- Created Pester v5 testing guidelines with setup/teardown patterns and assertion best practices
Reviewed Changes
Copilot reviewed 9 out of 10 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/instructions/prompt.instructions.md |
Guidelines for creating effective prompt files with frontmatter requirements and workflow structure |
.github/instructions/powershell.instructions.md |
PowerShell cmdlet development standards including naming, parameters, pipeline support, and error handling |
.github/instructions/powershell-pester-5.instructions.md |
Pester v5 testing conventions covering test structure, mocking, data-driven tests, and best practices |
.github/instructions/markdown.instructions.md |
Documentation standards for markdown content including formatting rules and validation requirements |
.github/instructions/localization.instructions.md |
Guidelines for localizing markdown documents with directory structure and disclaimer requirements |
.github/instructions/instructions.instructions.md |
Meta-guidelines for creating high-quality custom instruction files for GitHub Copilot |
.github/instructions/github-actions-ci-cd-best-practices.instructions.md |
Comprehensive CI/CD pipeline guidance covering security, optimization, testing, and deployment strategies |
.github/instructions/codacy.instructions.md |
Configuration for AI behavior when interacting with Codacy's MCP Server |
.github/instructions/a11y.instructions.md |
Accessibility guidelines for creating WCAG 2.2 Level AA compliant code |
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.
…on, markdown standards, PowerShell Pester testing, and cmdlet development best practices