chore(copilot): scaffold repo instructions#354
Merged
wax911 merged 3 commits intoAug 28, 2025
Conversation
Copilot
AI
changed the title
[WIP] chore(copilot): scaffold chat modes, prompts, and repo instructions
chore(copilot): scaffold chat modes, prompts, and repo instructions
Aug 24, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR scaffolds GitHub Copilot customization assets for the support-query-builder repository by implementing a comprehensive set of chat modes, prompts, and instructions to enhance the AI-assisted development experience.
- Establishes foundational GitHub Copilot infrastructure with chat modes, prompts, and repository-specific context instructions
- Creates extensive template system for specifications, implementation plans, and architectural decision records
- Updates contributing documentation to guide developers on using the new Copilot customization features
Reviewed Changes
Copilot reviewed 14 out of 14 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| CONTRIBUTING.md | Added GitHub Copilot customization section documenting new assets and conventional commit usage |
| .github/instructions/context.instructions.md | Created comprehensive project architecture documentation for AI context |
| .github/prompts/*.prompt.md | Added 7 structured prompt templates for specifications, plans, workflows, and commit messages |
| .github/chatmodes/*.chatmode.md | Implemented 6 specialized chat modes for different development scenarios |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
| - Include examples and edge cases where applicable. | ||
| - Ensure the document is self-contained and does not rely on external context. | ||
|
|
||
| The specification should be saved in the [/spec/](/spec/) directory and named according to the following convention: `[a-z0-9-]+.md`, where the name should be descriptive of the specification's content and starting with the highlevel purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design]. |
There was a problem hiding this comment.
Fix spelling error: 'highlevel' should be 'high-level'
Suggested change
| The specification should be saved in the [/spec/](/spec/) directory and named according to the following convention: `[a-z0-9-]+.md`, where the name should be descriptive of the specification's content and starting with the highlevel purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design]. | |
| The specification should be saved in the [/spec/](/spec/) directory and named according to the following convention: `[a-z0-9-]+.md`, where the name should be descriptive of the specification's content and starting with the high-level purpose, which is one of [schema, tool, data, infrastructure, process, architecture, or design]. |
| --- | ||
|
|
||
| # Introduction | ||
|
|
There was a problem hiding this comment.
The badge URL uses placeholder syntax that won't render correctly. Consider using actual status values or providing clearer instructions on how to replace these placeholders.
|
|
||
| ## Issue Content | ||
|
|
||
| - Title: [module:sub_module] Brief description of what the requiment is (if no sumodule then `[module]` will suffice) |
There was a problem hiding this comment.
Fix spelling errors: 'requiment' should be 'requirement' and 'sumodule' should be 'submodule'
Suggested change
| - Title: [module:sub_module] Brief description of what the requiment is (if no sumodule then `[module]` will suffice) | |
| - Title: [module:submodule] Brief description of what the requirement is (if no submodule then `[module]` will suffice) |
| - You MUST follow ALL Markdown best practices and conventions for this project | ||
| - You MUST update ALL Markdown links to sections if section names or locations change | ||
| - You WILL remove any invisible or hidden unicode characters | ||
| - You WILL AVOID overusing bolding (`*`) EXCEPT when needed for emphasis, e.g.: **CRITICAL**, You WILL ALWAYS follow these instructions |
There was a problem hiding this comment.
The instruction references markdown bolding syntax incorrectly. Markdown uses **text** for bold, not *text* (which is italics).
Suggested change
| - You WILL AVOID overusing bolding (`*`) EXCEPT when needed for emphasis, e.g.: **CRITICAL**, You WILL ALWAYS follow these instructions | |
| - You WILL AVOID overusing bolding (`**`) EXCEPT when needed for emphasis, e.g.: **CRITICAL**, You WILL ALWAYS follow these instructions |
Co-authored-by: wax911 <7859175+wax911@users.noreply.github.com>
5415aeb to
4c97574
Compare
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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 scaffolds GitHub Copilot customization assets for the support-query-builder repository by copying baseline configurations from AniTrend/anitrend-v2 and creating repo-specific instructions.
Changes Made
Created Repo-Specific Instructions
Context Instructions (
.github/instructions/context.instructions.md):core,core:ext,annotations,processorUpdated Documentation
CONTRIBUTING.md:
This scaffolding provides a foundation for enhanced GitHub Copilot interactions while respecting the project's specific architecture and documentation patterns.
Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
dl.google.com/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED -Xmx2048m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-9.0.0-bin/d6wjpkvcgsg3oed0qlfss3wgl/gradle-9.0.0/lib/gradle-daemon-main-9.0.0.jar -javaagent:/home/REDACTED/.gradle/wrapper/dists/gradle-9.0.0-bin/d6wjpkvcgsg3oed0qlfss3wgl/gradle-9.0.0/lib/agents/gradle-instrumentation-agent-9.0.0.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 9.0.0(dns block)www.jitpack.io/usr/lib/jvm/temurin-17-jdk-amd64/bin/java --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-opens=java.base/java.nio.charset=ALL-UNNAMED --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util.concurrent.atomic=ALL-UNNAMED --add-opens=java.xml/javax.xml.namespace=ALL-UNNAMED -Xmx2048m -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/REDACTED/.gradle/wrapper/dists/gradle-9.0.0-bin/d6wjpkvcgsg3oed0qlfss3wgl/gradle-9.0.0/lib/gradle-daemon-main-9.0.0.jar -javaagent:/home/REDACTED/.gradle/wrapper/dists/gradle-9.0.0-bin/d6wjpkvcgsg3oed0qlfss3wgl/gradle-9.0.0/lib/agents/gradle-instrumentation-agent-9.0.0.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 9.0.0(dns block)If you need me to access, download, or install something from one of these locations, you can either:
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.