suggest-awesome-github-copilot-instructions

Name: suggest-awesome-github-copilot-instructions
Author: github

8.7kinstalls4.6kforks

How to install suggest-awesome-github-copilot-instructions?

github/awesome-copilot/suggest-awesome-github-copilot-instructions

$npx -y skills add github/awesome-copilot --skill suggest-awesome-github-copilot-instructions

Installs into the current project.

Summary

suggest-awesome-github-copilot-instructions is an agent skill published from github/awesome-copilot, installable through the skills CLI.

Files · 1

View on GitHub

SKILL.md

1	# Suggest Awesome GitHub Copilot Instructions
2
3	Analyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository.
4
5	## Process
6
7	1. Fetch Available Instructions: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool.
8	2. Scan Local Instructions: Discover existing instruction files in `.github/instructions/` folder
9	3. Extract Descriptions: Read front matter from local instruction files to get descriptions and `applyTo` patterns
10	4. Fetch Remote Versions: For each local instruction, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`)
11	5. Compare Versions: Compare local instruction content with remote versions to identify:
12	- Instructions that are up-to-date (exact match)
13	- Instructions that are outdated (content differs)
14	- Key differences in outdated instructions (description, applyTo patterns, content)
15	6. Analyze Context: Review chat history, repository files, and current project needs
16	7. Compare Existing: Check against instructions already available in this repository
17	8. Match Relevance: Compare available instructions against identified patterns and requirements
18	9. Present Options: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions
19	10. Validate: Ensure suggested instructions would add value not already covered by existing instructions
20	11. Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
21	AWAIT user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
22	12. Download/Update Assets: For requested instructions, automatically:
23	- Download new instructions to `.github/instructions/` folder
24	- Update outdated instructions by replacing with latest version from awesome-copilot
25	- Do NOT adjust content of the files
26	- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
27	- Use `#todos` tool to track progress
28
29	## Context Analysis Criteria
30
31	🔍 Repository Patterns:
32	- Programming languages used (.cs, .js, .py, .ts, etc.)
33	- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
34	- Project types (web apps, APIs, libraries, tools)
35	- Development workflow requirements (testing, CI/CD, deployment)
36
37	🗨️ Chat History Context:
38	- Recent discussions and pain points
39	- Technology-specific questions
40	- Coding standards discussions
41	- Development workflow requirements
42
43	## Output Format
44
45	Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:
46
47	\| Awesome-Copilot Instruction \| Description \| Already Installed \| Similar Local Instruction \| Suggestion Rationale \|
48	\|------------------------------\|-------------\|-------------------\|---------------------------\|---------------------\|
49	\| [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) \| Blazor development guidelines \| ✅ Yes \| blazor.instructions.md \| Already covered by existing Blazor instructions \|
50	\| [reactjs.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/reactjs.instructions.md) \| ReactJS development standards \| ❌ No \| None \| Would enhance React development with established patterns \|
51	\| [java.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md) \| Java development best practices \| ⚠️ Outdated \| java.instructions.md \| applyTo pattern differs: remote uses `'*/.java'` vs local `'*.java'` - Update recommended \|
52
53	## Local Instructions Discovery Process
54
55	1. List all `*.instructions.md` files in the `instructions/` directory
56	2. For each discovered file, read front matter to extract `description` and `applyTo` patterns
57	3. Build comprehensive inventory of existing instructions with their applicable file patterns
58	4. Use this inventory to avoid suggesting duplicates
59
60	## Version Comparison Process
61
62	1. For each local instruction file, construct the raw GitHub URL to fetch the remote version:
63	- Pattern: `https://raw.githubusercontent.com/

People who liked this also viewed

6 picks

Type

suggest-awesome-github-copilot-instructions

8.7kinstalls4.6kforks

View on GitHub

How to install suggest-awesome-github-copilot-instructions?

github/awesome-copilot/suggest-awesome-github-copilot-instructions

$npx -y skills add github/awesome-copilot --skill suggest-awesome-github-copilot-instructions

Installs into the current project.

Summary

suggest-awesome-github-copilot-instructions is an agent skill published from github/awesome-copilot, installable through the skills CLI.

Files · 1

View on GitHub

SKILL.md

1	# Suggest Awesome GitHub Copilot Instructions
2
3	Analyze current repository context and suggest relevant copilot-instruction files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) that are not already available in this repository.
4
5	## Process
6
7	1. Fetch Available Instructions: Extract instruction list and descriptions from [awesome-copilot README.instructions.md](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md). Must use `#fetch` tool.
8	2. Scan Local Instructions: Discover existing instruction files in `.github/instructions/` folder
9	3. Extract Descriptions: Read front matter from local instruction files to get descriptions and `applyTo` patterns
10	4. Fetch Remote Versions: For each local instruction, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`)
11	5. Compare Versions: Compare local instruction content with remote versions to identify:
12	- Instructions that are up-to-date (exact match)
13	- Instructions that are outdated (content differs)
14	- Key differences in outdated instructions (description, applyTo patterns, content)
15	6. Analyze Context: Review chat history, repository files, and current project needs
16	7. Compare Existing: Check against instructions already available in this repository
17	8. Match Relevance: Compare available instructions against identified patterns and requirements
18	9. Present Options: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions
19	10. Validate: Ensure suggested instructions would add value not already covered by existing instructions
20	11. Output: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
21	AWAIT user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
22	12. Download/Update Assets: For requested instructions, automatically:
23	- Download new instructions to `.github/instructions/` folder
24	- Update outdated instructions by replacing with latest version from awesome-copilot
25	- Do NOT adjust content of the files
26	- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
27	- Use `#todos` tool to track progress
28
29	## Context Analysis Criteria
30
31	🔍 Repository Patterns:
32	- Programming languages used (.cs, .js, .py, .ts, etc.)
33	- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
34	- Project types (web apps, APIs, libraries, tools)
35	- Development workflow requirements (testing, CI/CD, deployment)
36
37	🗨️ Chat History Context:
38	- Recent discussions and pain points
39	- Technology-specific questions
40	- Coding standards discussions
41	- Development workflow requirements
42
43	## Output Format
44
45	Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:
46
47	\| Awesome-Copilot Instruction \| Description \| Already Installed \| Similar Local Instruction \| Suggestion Rationale \|
48	\|------------------------------\|-------------\|-------------------\|---------------------------\|---------------------\|
49	\| [blazor.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/blazor.instructions.md) \| Blazor development guidelines \| ✅ Yes \| blazor.instructions.md \| Already covered by existing Blazor instructions \|
50	\| [reactjs.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/reactjs.instructions.md) \| ReactJS development standards \| ❌ No \| None \| Would enhance React development with established patterns \|
51	\| [java.instructions.md](https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md) \| Java development best practices \| ⚠️ Outdated \| java.instructions.md \| applyTo pattern differs: remote uses `'*/.java'` vs local `'*.java'` - Update recommended \|
52
53	## Local Instructions Discovery Process
54
55	1. List all `*.instructions.md` files in the `instructions/` directory
56	2. For each discovered file, read front matter to extract `description` and `applyTo` patterns
57	3. Build comprehensive inventory of existing instructions with their applicable file patterns
58	4. Use this inventory to avoid suggesting duplicates
59
60	## Version Comparison Process
61
62	1. For each local instruction file, construct the raw GitHub URL to fetch the remote version:
63	- Pattern: `https://raw.githubusercontent.com/

People who liked this also viewed

6 picks

Type