Refine AI context files#88
Open
ai-coding-guardrails-jon-sandbox[bot] wants to merge 1 commit intomainfrom
Open
Refine AI context files#88ai-coding-guardrails-jon-sandbox[bot] wants to merge 1 commit intomainfrom
ai-coding-guardrails-jon-sandbox[bot] wants to merge 1 commit intomainfrom
Conversation
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.
This PR contains suggested improvements to AI context files.
Summary
.github/copilot-instructions.mdThe file is generally well-structured but is missing explicit guidance on four key requirements: (1) validating URL parameters before parsing, (2) updating tests when methods change, (5) completing the testing checklist before feature removal. Security section also lacks input validation guidance. Four targeted edits address these gaps.
CONTRIBUTING.mdThe CONTRIBUTING.md is mostly a procedural guide with no security, testing-update, or input-validation guidance. Two edits are suggested: (1) a pre-PR checklist that surfaces requirements around test maintenance and URL parameter validation, and (2) an inline note in the testing section reinforcing the test-update requirement. No existing content needs to be removed; the additions are concise and actionable.