| file_type | instructions | |||||
|---|---|---|---|---|---|---|
| title | Prompt File Instructions | |||||
| description | Guidelines for creating high-quality prompt files for GitHub Copilot and reusable AI workflows | |||||
| scope | repo-local | |||||
| version | v1.0 | |||||
| last_updated | 2026-05-29 | |||||
| owners |
|
|||||
| tags |
|
|||||
| applyTo |
|
|||||
| status | active |
Create reusable, well-structured prompt files for GitHub Copilot and AI workflows. Prompts should be modular, context-aware, and aligned with project standards.
- Prompt files use
.prompt.mdextension for discoverability - Follow YAML frontmatter with clear metadata
- Include system role, context, and expected output format
- Use placeholders (
{{variable}}) for dynamic content - Keep prompts focused on a single task or workflow
- Document required inputs and expected outputs
title— Clear, descriptive title of the promptdescription— One-sentence summaryversion— Semantic version (v1.0, v1.1, etc.)scope— "organization-wide" or "repo-local"role— Primary use case (e.g., "code-review", "documentation")tags— Searchable keywordsinputs— Required variables and their descriptionsoutputs— Expected output format and structure
- System Role — Define the Copilot persona and responsibilities
- Context — Provide background and constraints
- Task — Clear, actionable instructions
- Output Format — Expected format (Markdown, JSON, etc.)
- Examples — Optional examples of expected output
Use double-brace syntax for variables: {{variable_name}}
Common variables:
{{file_path}}— File being edited{{language}}— Programming language{{context}}— User-provided context{{standards}}— Applicable coding standards
All prompt files must:
- Pass Markdown linting
- Have valid YAML frontmatter
- Include description and role fields
- Use consistent formatting
- custom-instructions.md — Main Copilot instructions for this repository
- prompts/ — Prompt file collection and index