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.
- What We Accept
- What We Don't Accept
- Quality Guidelines
- How to Contribute
- Submitting Your Contribution
- Contributor Recognition
- Code of Conduct
- License
We welcome contributions covering any technology, framework, or development practice that helps developers work more effectively with GitHub Copilot. This includes:
- Programming languages and frameworks
- Development methodologies and best practices
- Architecture patterns and design principles
- Testing strategies and quality assurance
- DevOps and deployment practices
- Accessibility and inclusive design
- Performance optimization techniques
If you are planning to contribute content that involves paid services, please review our Guidance for submissions involving paid services.
To maintain a safe, responsible, and high-signal collection, we will not accept contributions that:
- Violate Responsible AI Principles: Content that attempts to circumvent Microsoft/GitHub's Responsible AI guidelines or promotes harmful AI usage
- Compromise Security: Instructions designed to bypass security policies, exploit vulnerabilities, or weaken system security
- Enable Malicious Activities: Content intended to harm other systems, users, or organizations
- Exploit Weaknesses: Instructions that take advantage of vulnerabilities in other platforms or services
- Promote Harmful Content: Guidance that could lead to the creation of harmful, discriminatory, or inappropriate content
- Circumvent Platform Policies: Attempts to work around GitHub, Microsoft, or other platform terms of service
- Duplicate Existing Model Strengths Without Meaningful Uplift: Submissions that mainly tell Copilot to do work frontier models already handle well (for example, generic TypeScript, HTML, or other broadly-supported coding tasks) without addressing a clear gap, specialized workflow, or domain-specific constraint. These contributions are often lower value for users and can introduce weaker or conflicting guidance than the model's default behavior.
- Unreviewed remote-source plugins: Do not open a pull request that directly adds a third-party plugin to
plugins/external.json. Public external plugins must use the review workflow documented below. In v1, that workflow only accepts plugins hosted in public GitHub repositories; non-GitHub sources such as generic git URLs are not accepted for public submissions.
- Be specific: Generic instructions are less helpful than specific, actionable guidance
- Test your content: Ensure your instructions or skills work well with GitHub Copilot
- Follow conventions: Use consistent formatting and naming
- Keep it focused: Each file should address a specific technology, framework, or use case
- Write clearly: Use simple, direct language
- Promote best practices: Encourage secure, maintainable, and ethical development practices
Instructions help customize GitHub Copilot's behavior for specific technologies, coding practices, or domains.