You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+7-23Lines changed: 7 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,9 @@
2
2
3
3
## Project Overview
4
4
5
-
The Awesome GitHub Copilot repository is a community-driven collection of custom agents, prompts, and instructions designed to enhance GitHub Copilot experiences across various domains, languages, and use cases. The project includes:
5
+
The Awesome GitHub Copilot repository is a community-driven collection of custom agents and instructions designed to enhance GitHub Copilot experiences across various domains, languages, and use cases. The project includes:
6
6
7
7
-**Agents** - Specialized GitHub Copilot agents that integrate with MCP servers
8
-
-**Prompts** - Task-specific prompts for code generation and problem-solving
9
8
-**Instructions** - Coding standards and best practices applied to specific file patterns
10
9
-**Skills** - Self-contained folders with instructions and bundled resources for specialized tasks
11
10
-**Hooks** - Automated workflows triggered by specific events during development
@@ -17,7 +16,6 @@ The Awesome GitHub Copilot repository is a community-driven collection of custom
@@ -55,23 +53,16 @@ npm run skill:create -- --name <skill-name>
55
53
56
54
## Development Workflow
57
55
58
-
### Working with Agents, Prompts, Instructions, Skills, and Hooks
56
+
### Working with Agents, Instructions, Skills, and Hooks
59
57
60
-
All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets. Hooks are folders containing a `README.md` with frontmatter and a `hooks.json` configuration file:
58
+
All agent files (`*.agent.md`) and instruction files (`*.instructions.md`) must include proper markdown front matter. Agent Skills are folders containing a `SKILL.md` file with frontmatter and optional bundled assets. Hooks are folders containing a `README.md` with frontmatter and a `hooks.json` configuration file:
61
59
62
60
#### Agent Files (*.agent.md)
63
61
- Must have `description` field (wrapped in single quotes)
64
62
- File names should be lower case with words separated by hyphens
65
63
- Recommended to include `tools` field
66
64
- Strongly recommended to specify `model` field
67
65
68
-
#### Prompt Files (*.prompt.md)
69
-
- Must have `agent` field (value should be `'agent'` wrapped in single quotes)
70
-
- Must have `description` field (wrapped in single quotes, not empty)
71
-
- File names should be lower case with words separated by hyphens
72
-
- Recommended to specify `tools` if applicable
73
-
- Strongly recommended to specify `model` field
74
-
75
66
#### Instruction Files (*.instructions.md)
76
67
- Must have `description` field (wrapped in single quotes, not empty)
77
68
- Must have `applyTo` field specifying file patterns (e.g., `'**.js, **.ts'`)
@@ -120,9 +111,9 @@ All agent files (`*.agent.md`), prompt files (`*.prompt.md`), and instruction fi
120
111
121
112
### Adding New Resources
122
113
123
-
When adding a new agent, prompt, instruction, skill, hook, workflow, or plugin:
114
+
When adding a new agent, instruction, skill, hook, workflow, or plugin:
124
115
125
-
**For Agents, Prompts, and Instructions:**
116
+
**For Agents and Instructions:**
126
117
1. Create the file with proper front matter
127
118
2. Add the file to the appropriate directory
128
119
3. Update the README.md by running: `npm run build`
@@ -207,7 +198,7 @@ When creating a pull request:
207
198
3.**File naming**: Verify all new files follow the lower-case-with-hyphens naming convention
208
199
4.**Build check**: Run `npm run build` before committing to verify README generation
209
200
5.**Line endings**: **Always run `bash scripts/fix-line-endings.sh`** to normalize line endings to LF (Unix-style)
210
-
6.**Description**: Provide a clear description of what your agent/prompt/instruction does
201
+
6.**Description**: Provide a clear description of what your agent/instruction does
211
202
7.**Testing**: If adding a plugin, run `npm run plugin:validate` to ensure validity
212
203
213
204
### Pre-commit Checklist
@@ -222,13 +213,6 @@ Before submitting your PR, ensure you have:
222
213
223
214
### Code Review Checklist
224
215
225
-
For prompt files (*.prompt.md):
226
-
-[ ] Has markdown front matter
227
-
-[ ] Has `agent` field (value should be `'agent'` wrapped in single quotes)
228
-
-[ ] Has non-empty `description` field wrapped in single quotes
229
-
-[ ] File name is lower case with hyphens
230
-
-[ ] Includes `model` field (strongly recommended)
231
-
232
216
For instruction files (*.instructions.md):
233
217
-[ ] Has markdown front matter
234
218
-[ ] Has non-empty `description` field wrapped in single quotes
@@ -295,7 +279,7 @@ This is a community-driven project. Contributions are welcome! Please see:
295
279
296
280
## MCP Server
297
281
298
-
The repository includes an MCP (Model Context Protocol) Server that provides prompts for searching and installing resources directly from this repository. Docker is required to run the server.
282
+
The repository includes an MCP (Model Context Protocol) Server for searching and installing resources directly from this repository. Docker is required to run the server.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+9-34Lines changed: 9 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Contributing to Awesome GitHub Copilot
2
2
3
-
Thank you for your interest in contributing to the Awesome GitHub Copilot repository! We welcome contributions from the community to help expand our collection of custom instructions and prompts.
3
+
Thank you for your interest in contributing to the Awesome GitHub Copilot repository! We welcome contributions from the community to help expand our collection of custom instructions and skills.
4
4
5
5
## How to Contribute
6
6
@@ -33,34 +33,6 @@ description: 'Instructions for customizing GitHub Copilot behavior for specific
33
33
- Any additional context or examples
34
34
```
35
35
36
-
### Adding Prompts
37
-
38
-
Prompts are ready-to-use templates for specific development scenarios and tasks.
39
-
40
-
1.**Create your prompt file**: Add a new `.prompt.md` file in the `prompts/` directory
41
-
2.**Follow the naming convention**: Use descriptive, lowercase filenames with hyphens and the `.prompt.md` extension (e.g., `react-component-generator.prompt.md`)
42
-
3.**Include frontmatter**: Add metadata at the top of your file (optional but recommended)
43
-
4.**Structure your prompt**: Provide clear context and specific instructions
44
-
45
-
#### Example prompt format
46
-
47
-
```markdown
48
-
---
49
-
agent: 'agent'
50
-
tools: ['codebase', 'terminalCommand']
51
-
description: 'Brief description of what this prompt does'
52
-
---
53
-
54
-
# Prompt Title
55
-
56
-
Your goal is to...
57
-
58
-
## Specific Instructions
59
-
60
-
- Clear, actionable instructions
61
-
- Include examples where helpful
62
-
```
63
-
64
36
### Adding an Agent
65
37
66
38
Agents are specialized configurations that transform GitHub Copilot Chat into domain-specific assistants or personas for particular development scenarios.
@@ -113,7 +85,7 @@ Skills are self-contained folders in the `skills/` directory that include a `SKI
113
85
114
86
### Adding Plugins
115
87
116
-
Plugins group related agents, commands (prompts), and skills around specific themes or workflows, making it easy for users to install comprehensive toolkits via GitHub Copilot CLI.
88
+
Plugins group related agents, commands, and skills around specific themes or workflows, making it easy for users to install comprehensive toolkits via GitHub Copilot CLI.
117
89
118
90
1.**Create your plugin**: Run `npm run plugin:create` to scaffold a new plugin
119
91
2.**Follow the naming convention**: Use descriptive, lowercase folder names with hyphens (e.g., `python-web-development`)
@@ -215,13 +187,13 @@ Create a daily summary of open issues for the team.
215
187
216
188
1.**Fork this repository**
217
189
2.**Create a new branch** for your contribution
218
-
3.**Add your instruction, prompt file, chatmode, workflow, or plugin** following the guidelines above
190
+
3.**Add your instruction, skills, agents, workflow, or plugin** following the guidelines above
219
191
4.**Run the update script**: `npm start` to update the README with your new file (make sure you run `npm install` first if you haven't already)
220
192
- A GitHub Actions workflow will verify that this step was performed correctly
221
193
- If the README.md would be modified by running the script, the PR check will fail with a comment showing the required changes
222
194
5.**Submit a pull request** targeting the `staged` branch with:
223
195
- A clear title describing your contribution
224
-
- A brief description of what your instruction/prompt does
196
+
- A brief description of what your instruction/skill/agent does
225
197
- Any relevant context or usage notes
226
198
227
199
> [!IMPORTANT]
@@ -256,7 +228,7 @@ To maintain a safe, responsible, and constructive community, we will **not accep
256
228
## Quality Guidelines
257
229
258
230
-**Be specific**: Generic instructions are less helpful than specific, actionable guidance
259
-
-**Test your content**: Ensure your instructions or prompts work well with GitHub Copilot
231
+
-**Test your content**: Ensure your instructions or skills work well with GitHub Copilot
260
232
-**Follow conventions**: Use consistent formatting and naming
261
233
-**Keep it focused**: Each file should address a specific technology, framework, or use case
262
234
-**Write clearly**: Use simple, direct language
@@ -281,11 +253,14 @@ We welcome many kinds of contributions, including the custom categories below:
0 commit comments