Skip to content

Commit ccc6997

Browse files
github-actions[bot]github-actions[bot]
committed
chore: publish from staged [skip ci]
1 parent b2404ea commit ccc6997

185 files changed

Lines changed: 33454 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎plugins/awesome-copilot/agents/meta-agentic-project-scaffold.md‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
description: "Meta agentic project creation assistant to help users create and manage project workflows effectively."
3+
name: "Meta Agentic Project Scaffold"
4+
tools: ["changes", "codebase", "edit/editFiles", "extensions", "fetch", "findTestFiles", "githubRepo", "new", "openSimpleBrowser", "problems", "readCellOutput", "runCommands", "runNotebooks", "runTasks", "runTests", "search", "searchResults", "terminalLastCommand", "terminalSelection", "testFailure", "updateUserPreferences", "usages", "vscodeAPI", "activePullRequest", "copilotCodingAgent"]
5+
model: "GPT-4.1"
6+
---
7+
8+
Your sole task is to find and pull relevant prompts, instructions and chatmodes from https://github.com/github/awesome-copilot
9+
All relevant instructions, prompts and chatmodes that might be able to assist in an app development, provide a list of them with their vscode-insiders install links and explainer what each does and how to use it in our app, build me effective workflows
10+
11+
For each please pull it and place it in the right folder in the project
12+
Do not do anything else, just pull the files
13+
At the end of the project, provide a summary of what you have done and how it can be used in the app development process
14+
Make sure to include the following in your summary: list of workflows which are possible by these prompts, instructions and chatmodes, how they can be used in the app development process, and any additional insights or recommendations for effective project management.
15+
16+
Do not change or summarize any of the tools, copy and place them as is

‎plugins/awesome-copilot/commands/suggest-awesome-github-copilot-agents.md‎

Lines changed: 107 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,107 @@
1+
---
2+
agent: "agent"
3+
description: "Suggest relevant GitHub Copilot Custom Agents files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing custom agents in this repository, and identifying outdated agents that need updates."
4+
tools: ["edit", "search", "runCommands", "runTasks", "changes", "testFailure", "openSimpleBrowser", "fetch", "githubRepo", "todos"]
5+
---
6+
7+
# Suggest Awesome GitHub Copilot Custom Agents
8+
9+
Analyze current repository context and suggest relevant Custom Agents files from the [GitHub awesome-copilot repository](https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md) that are not already available in this repository. Custom Agent files are located in the [agents](https://github.com/github/awesome-copilot/tree/main/agents) folder of the awesome-copilot repository.
10+
11+
## Process
12+
13+
1. **Fetch Available Custom Agents**: Extract Custom Agents list and descriptions from [awesome-copilot README.agents.md](https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md). Must use `fetch` tool.
14+
2. **Scan Local Custom Agents**: Discover existing custom agent files in `.github/agents/` folder
15+
3. **Extract Descriptions**: Read front matter from local custom agent files to get descriptions
16+
4. **Fetch Remote Versions**: For each local agent, fetch the corresponding version from awesome-copilot repository using raw GitHub URLs (e.g., `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>`)
17+
5. **Compare Versions**: Compare local agent content with remote versions to identify:
18+
- Agents that are up-to-date (exact match)
19+
- Agents that are outdated (content differs)
20+
- Key differences in outdated agents (tools, description, content)
21+
6. **Analyze Context**: Review chat history, repository files, and current project needs
22+
7. **Match Relevance**: Compare available custom agents against identified patterns and requirements
23+
8. **Present Options**: Display relevant custom agents with descriptions, rationale, and availability status including outdated agents
24+
9. **Validate**: Ensure suggested agents would add value not already covered by existing agents
25+
10. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot custom agents and similar local custom agents
26+
**AWAIT** user request to proceed with installation or updates of specific custom agents. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
27+
11. **Download/Update Assets**: For requested agents, automatically:
28+
- Download new agents to `.github/agents/` folder
29+
- Update outdated agents by replacing with latest version from awesome-copilot
30+
- Do NOT adjust content of the files
31+
- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
32+
- Use `#todos` tool to track progress
33+
34+
## Context Analysis Criteria
35+
36+
🔍 **Repository Patterns**:
37+
38+
- Programming languages used (.cs, .js, .py, etc.)
39+
- Framework indicators (ASP.NET, React, Azure, etc.)
40+
- Project types (web apps, APIs, libraries, tools)
41+
- Documentation needs (README, specs, ADRs)
42+
43+
🗨️ **Chat History Context**:
44+
45+
- Recent discussions and pain points
46+
- Feature requests or implementation needs
47+
- Code review patterns
48+
- Development workflow requirements
49+
50+
## Output Format
51+
52+
Display analysis results in structured table comparing awesome-copilot custom agents with existing repository custom agents:
53+
54+
| Awesome-Copilot Custom Agent | Description | Already Installed | Similar Local Custom Agent | Suggestion Rationale |
55+
| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | ---------------------------------- | ------------------------------------------------------------- |
56+
| [amplitude-experiment-implementation.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/amplitude-experiment-implementation.agent.md) | This custom agent uses Amplitude's MCP tools to deploy new experiments inside of Amplitude, enabling seamless variant testing capabilities and rollout of product features | ❌ No | None | Would enhance experimentation capabilities within the product |
57+
| [launchdarkly-flag-cleanup.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/launchdarkly-flag-cleanup.agent.md) | Feature flag cleanup agent for LaunchDarkly | ✅ Yes | launchdarkly-flag-cleanup.agent.md | Already covered by existing LaunchDarkly custom agents |
58+
| [principal-software-engineer.agent.md](https://github.com/github/awesome-copilot/blob/main/agents/principal-software-engineer.agent.md) | Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation. | ⚠️ Outdated | principal-software-engineer.agent.md | Tools configuration differs: remote uses `'web/fetch'` vs local `'fetch'` - Update recommended |
59+
60+
## Local Agent Discovery Process
61+
62+
1. List all `*.agent.md` files in `.github/agents/` directory
63+
2. For each discovered file, read front matter to extract `description`
64+
3. Build comprehensive inventory of existing agents
65+
4. Use this inventory to avoid suggesting duplicates
66+
67+
## Version Comparison Process
68+
69+
1. For each local agent file, construct the raw GitHub URL to fetch the remote version:
70+
- Pattern: `https://raw.githubusercontent.com/github/awesome-copilot/main/agents/<filename>`
71+
2. Fetch the remote version using the `fetch` tool
72+
3. Compare entire file content (including front matter, tools array, and body)
73+
4. Identify specific differences:
74+
- **Front matter changes** (description, tools)
75+
- **Tools array modifications** (added, removed, or renamed tools)
76+
- **Content updates** (instructions, examples, guidelines)
77+
5. Document key differences for outdated agents
78+
6. Calculate similarity to determine if update is needed
79+
80+
## Requirements
81+
82+
- Use `githubRepo` tool to get content from awesome-copilot repository agents folder
83+
- Scan local file system for existing agents in `.github/agents/` directory
84+
- Read YAML front matter from local agent files to extract descriptions
85+
- Compare local agents with remote versions to detect outdated agents
86+
- Compare against existing agents in this repository to avoid duplicates
87+
- Focus on gaps in current agent library coverage
88+
- Validate that suggested agents align with repository's purpose and standards
89+
- Provide clear rationale for each suggestion
90+
- Include links to both awesome-copilot agents and similar local agents
91+
- Clearly identify outdated agents with specific differences noted
92+
- Don't provide any additional information or context beyond the table and the analysis
93+
94+
## Icons Reference
95+
96+
- ✅ Already installed and up-to-date
97+
- ⚠️ Installed but outdated (update available)
98+
- ❌ Not installed in repo
99+
100+
## Update Handling
101+
102+
When outdated agents are identified:
103+
1. Include them in the output table with ⚠️ status
104+
2. Document specific differences in the "Suggestion Rationale" column
105+
3. Provide recommendation to update with key changes noted
106+
4. When user requests update, replace entire local file with remote version
107+
5. Preserve file location in `.github/agents/` directory

‎plugins/awesome-copilot/commands/suggest-awesome-github-copilot-instructions.md‎

Lines changed: 122 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,122 @@
1+
---
2+
agent: 'agent'
3+
description: 'Suggest relevant GitHub Copilot instruction files from the awesome-copilot repository based on current repository context and chat history, avoiding duplicates with existing instructions in this repository, and identifying outdated instructions that need updates.'
4+
tools: ['edit', 'search', 'runCommands', 'runTasks', 'think', 'changes', 'testFailure', 'openSimpleBrowser', 'web/fetch', 'githubRepo', 'todos', 'search']
5+
---
6+
# Suggest Awesome GitHub Copilot Instructions
7+
8+
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.
9+
10+
## Process
11+
12+
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.
13+
2. **Scan Local Instructions**: Discover existing instruction files in `.github/instructions/` folder
14+
3. **Extract Descriptions**: Read front matter from local instruction files to get descriptions and `applyTo` patterns
15+
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>`)
16+
5. **Compare Versions**: Compare local instruction content with remote versions to identify:
17+
- Instructions that are up-to-date (exact match)
18+
- Instructions that are outdated (content differs)
19+
- Key differences in outdated instructions (description, applyTo patterns, content)
20+
6. **Analyze Context**: Review chat history, repository files, and current project needs
21+
7. **Compare Existing**: Check against instructions already available in this repository
22+
8. **Match Relevance**: Compare available instructions against identified patterns and requirements
23+
9. **Present Options**: Display relevant instructions with descriptions, rationale, and availability status including outdated instructions
24+
10. **Validate**: Ensure suggested instructions would add value not already covered by existing instructions
25+
11. **Output**: Provide structured table with suggestions, descriptions, and links to both awesome-copilot instructions and similar local instructions
26+
**AWAIT** user request to proceed with installation or updates of specific instructions. DO NOT INSTALL OR UPDATE UNLESS DIRECTED TO DO SO.
27+
12. **Download/Update Assets**: For requested instructions, automatically:
28+
- Download new instructions to `.github/instructions/` folder
29+
- Update outdated instructions by replacing with latest version from awesome-copilot
30+
- Do NOT adjust content of the files
31+
- Use `#fetch` tool to download assets, but may use `curl` using `#runInTerminal` tool to ensure all content is retrieved
32+
- Use `#todos` tool to track progress
33+
34+
## Context Analysis Criteria
35+
36+
🔍 **Repository Patterns**:
37+
- Programming languages used (.cs, .js, .py, .ts, etc.)
38+
- Framework indicators (ASP.NET, React, Azure, Next.js, etc.)
39+
- Project types (web apps, APIs, libraries, tools)
40+
- Development workflow requirements (testing, CI/CD, deployment)
41+
42+
🗨️ **Chat History Context**:
43+
- Recent discussions and pain points
44+
- Technology-specific questions
45+
- Coding standards discussions
46+
- Development workflow requirements
47+
48+
## Output Format
49+
50+
Display analysis results in structured table comparing awesome-copilot instructions with existing repository instructions:
51+
52+
| Awesome-Copilot Instruction | Description | Already Installed | Similar Local Instruction | Suggestion Rationale |
53+
|------------------------------|-------------|-------------------|---------------------------|---------------------|
54+
| [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 |
55+
| [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 |
56+
| [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 |
57+
58+
## Local Instructions Discovery Process
59+
60+
1. List all `*.instructions.md` files in the `instructions/` directory
61+
2. For each discovered file, read front matter to extract `description` and `applyTo` patterns
62+
3. Build comprehensive inventory of existing instructions with their applicable file patterns
63+
4. Use this inventory to avoid suggesting duplicates
64+
65+
## Version Comparison Process
66+
67+
1. For each local instruction file, construct the raw GitHub URL to fetch the remote version:
68+
- Pattern: `https://raw.githubusercontent.com/github/awesome-copilot/main/instructions/<filename>`
69+
2. Fetch the remote version using the `#fetch` tool
70+
3. Compare entire file content (including front matter and body)
71+
4. Identify specific differences:
72+
- **Front matter changes** (description, applyTo patterns)
73+
- **Content updates** (guidelines, examples, best practices)
74+
5. Document key differences for outdated instructions
75+
6. Calculate similarity to determine if update is needed
76+
77+
## File Structure Requirements
78+
79+
Based on GitHub documentation, copilot-instructions files should be:
80+
- **Repository-wide instructions**: `.github/copilot-instructions.md` (applies to entire repository)
81+
- **Path-specific instructions**: `.github/instructions/NAME.instructions.md` (applies to specific file patterns via `applyTo` frontmatter)
82+
- **Community instructions**: `instructions/NAME.instructions.md` (for sharing and distribution)
83+
84+
## Front Matter Structure
85+
86+
Instructions files in awesome-copilot use this front matter format:
87+
```markdown
88+
---
89+
description: 'Brief description of what this instruction provides'
90+
applyTo: '**/*.js,**/*.ts' # Optional: glob patterns for file matching
91+
---
92+
```
93+
94+
## Requirements
95+
96+
- Use `githubRepo` tool to get content from awesome-copilot repository instructions folder
97+
- Scan local file system for existing instructions in `.github/instructions/` directory
98+
- Read YAML front matter from local instruction files to extract descriptions and `applyTo` patterns
99+
- Compare local instructions with remote versions to detect outdated instructions
100+
- Compare against existing instructions in this repository to avoid duplicates
101+
- Focus on gaps in current instruction library coverage
102+
- Validate that suggested instructions align with repository's purpose and standards
103+
- Provide clear rationale for each suggestion
104+
- Include links to both awesome-copilot instructions and similar local instructions
105+
- Clearly identify outdated instructions with specific differences noted
106+
- Consider technology stack compatibility and project-specific needs
107+
- Don't provide any additional information or context beyond the table and the analysis
108+
109+
## Icons Reference
110+
111+
- ✅ Already installed and up-to-date
112+
- ⚠️ Installed but outdated (update available)
113+
- ❌ Not installed in repo
114+
115+
## Update Handling
116+
117+
When outdated instructions are identified:
118+
1. Include them in the output table with ⚠️ status
119+
2. Document specific differences in the "Suggestion Rationale" column
120+
3. Provide recommendation to update with key changes noted
121+
4. When user requests update, replace entire local file with remote version
122+
5. Preserve file location in `.github/instructions/` directory

0 commit comments

Comments
 (0)