github-copilot-starter
Helps your agent set up GitHub Copilot for a new project. It defines the coding tools the agent will use.
What it does
This tool sets up GitHub Copilot for your project. It creates instruction and organization files to help Copilot understand and follow your project's rules, like programming language and coding style.
When to use it
- ✓When starting a new programming project.
- ✓When you want GitHub Copilot to follow specific project rules.
- ✓To organize your team's coding guidelines.
Example of what to ask your AI
“Set up GitHub Copilot for a Python Django web project using PostgreSQL and Pytest for testing. The development style is flexible.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
The tool asks about your project's technology and then creates configuration files like '.github/copilot-instructions.md' and others within folders like '.github/instructions/' and '.github/skills/'. If you use GitHub Actions, it also sets up a workflow file.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add github/awesome-copilot --skill github-copilot-starterOr download just the file:
curl -L https://raw.githubusercontent.com/github/awesome-copilot/main/skills/github-copilot-starter/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
You are a GitHub Copilot setup specialist. Your task is to create a complete, production-ready GitHub Copilot configuration for a new project based on the specified technology stack.
Project Information Required
Ask the user for the following information if not provided:
- Primary Language/Framework: (e.g., JavaScript/React, Python/Django, Java/Spring Boot, etc.)
- Project Type: (e.g., web app, API, mobile app, desktop app, library, etc.)
- Additional Technologies: (e.g., database, cloud provider, testing frameworks, etc.)
- Development Style: (strict standards, flexible, specific patterns)
- GitHub Actions / Coding Agent: Does the project use GitHub Actions? (yes/no — determines whether to generate
copilot-setup-steps.yml)
Configuration Files to Create
Based on the provided stack, create the following files in the appropriate directories:
1. .github/copilot-instructions.md
Main repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.
Use this structure:
# {Project Name} — Copilot Instructions
## Project Overview
Brief description of what this project does and its primary purpose.
## Tech Stack
List the primary language, frameworks, and key dependencies.
## Conventions
- Naming: describe naming conventions for files, functions, variables
- Structure: describe how the codebase is organized
- Error handling: describe the project's approach to errors and exceptions
## Workflow
- Describe PR conventions, branch naming, and commit style
- Reference specific instruction files for detailed standards:
- Language guidelines: `.github/instructions/{language}.instructions.md`
- Testing: `.github/instructions/testing.instructions.md`
- Security: `.github/instructions/security.instructions.md`
- Documentation: `.github/instructions/documentation.instructions.md`
- Performance: `.github/instructions/performance.instructions.md`
- Code review: `.github/instructions/code-review.instructions.md`
2. .github/instructions/ Directory
Create specific instruction files:
{primaryLanguage}.instructions.md- Language-specific guidelinestesting.instructions.md- Testing standards and practicesdocumentation.instructions.md- Documentation requirementssecurity.instructions.md- Security best practicesperformance.instructions.md- Performance optimization guidelinescode-review.instructions.md- Code review standards and GitHub review guidelines
3. .github/skills/ Directory
Create reusable skills as self-contained folders:
setup-component/SKILL.md- Component/module creationwrite-tests/SKILL.md- Test generationcode-review/SKILL.md- Code review assistancerefactor-code/SKILL.md- Code refactoringgenerate-docs/SKILL.md- Documentation generationdebug-issue/SKILL.md- Debugging assistance
4. .github/agents/ Directory
Always create these 4 agents:
software-engineer.agent.mdarchitect.agent.mdreviewer.agent.mddebugger.agent.md
For each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.
Agent Attribution: When using content from awesome-copilot agents, add attribution comments:
<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/agents/[filename].agent.md -->
5. .github/workflows/ Directory (only if user uses GitHub Actions)
Skip this section entirely if the user answered "no" to GitHub Actions.
Create Coding Agent workflow file:
copilot-setup-steps.yml- GitHub Actions workflow for Coding Agent environment setup
CRITICAL: The workflow MUST follow this exact structure:
- Job name MUST be
copilot-setup-steps - Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)
- Set appropriate permissions (minimum required)
- Customize steps based on the technology stack provided
Content Guidelines
For each file, follow these principles:
MANDATORY FIRST STEP: Always use the fetch tool to research existing patterns before creating any content:
- Fetch specific instruction from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md
- Fetch specific agents from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md
…
FAQ
What is GitHub Copilot?
It's an AI tool that suggests code as you type, helping you program faster.
Why do I need to configure Copilot?
Configuration helps Copilot understand your project's rules and style, leading to more accurate and useful suggestions.
What are 'agents' and 'skills'?
Agents are AI profiles (like a 'software engineer') and skills are specific tasks (like 'write tests') that help Copilot perform more complex jobs.
Details
Original description by the author
Set up complete GitHub Copilot configuration for a new project based on technology stack
repo: github/awesome-copilot
Popularity
- GitHub stars
- 40k
- Ranking position
- #5171
- License
- MIT
- Updated
- 10/15/2026
Comments
- …
More skills from this repository
acquire-codebase-knowledge
Helps your agent understand and document an existing code project. It's useful for onboarding new people or getting an overview of the architecture.
github/awesome-copilot
acreadiness-assess
Enables your agent to assess a project's readiness for AI and generate a report. It's useful for understanding how well a project is prepared to use AI tools.
github/awesome-copilot
acreadiness-generate-instructions
Helps your agent create instructions for AI tools based on an assessment. It's useful for improving how AI interacts with code and closing identified gaps.
github/awesome-copilot
acreadiness-policy
Enables your agent to help define or apply policies for AI project assessment. It's useful for standardizing how projects are evaluated and ensuring compliance.
github/awesome-copilot
Similar skills
benchmark-optimization-loop
Has your agent improve something's speed in a measured way. It tests multiple versions and chooses the fastest one that still works correctly.
affaan-m/ECC
change-impact
Helps your agent analyze the impact of code changes before making them. It compares the planned vs. actual results afterward, covering paths, data, tests, and documentation. Useful for risky or system-wide changes.
affaan-m/ECC
click-path-audit
Lets your agent trace all user buttons and interactions to find bugs. It finds issues where functions seem to work alone but fail together. Useful when bugs persist even after debugging.
affaan-m/ECC