Github Copilot Starter
Bootstrap production-ready GitHub Copilot repo instructions and related config from your stack, project type, and whether GitHub Actions drives coding agents.
Overview
GitHub Copilot Starter is an agent skill for the Build phase that sets up complete GitHub Copilot configuration for a new project based on the technology stack.
Install
npx skills add https://github.com/github/awesome-copilot --skill github-copilot-starterWhat is this skill?
- Collects language, project type, extra tech, dev style, and GitHub Actions usage before generating files
- Creates `.github/copilot-instructions.md` as the primary always-on repository instruction surface
- Generates stack-aware configuration across the standard Copilot file set for new projects
- Conditionally includes `copilot-setup-steps.yml` when the project uses GitHub Actions as a coding agent
- Structured sections: project overview, tech stack, and naming conventions for repeatable Copilot behavior
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are starting a repo but Copilot has no durable instructions, so suggestions ignore your stack, naming, and whether Actions should bootstrap the coding agent.
Who is it for?
Solo founders or small teams spinning up a new codebase who want Copilot aligned to stack and conventions before the first feature merge.
Skip if: Mature repos that only need a one-line tweak to existing Copilot files, or teams not using GitHub Copilot at all.
When should I use this skill?
Set up complete GitHub Copilot configuration for a new project based on technology stack.
What do I get? / Deliverables
You get a production-oriented Copilot file set—including repository instructions and optional Actions setup—tailored to your declared stack and workflow.
- .github/copilot-instructions.md
- Additional stack-matched Copilot configuration files
- Optional copilot-setup-steps.yml when Actions is enabled
Recommended Skills
Journey fit
Copilot configuration is part of Build agent-tooling so every chat and PR interaction inherits consistent repo context from day one. Agent-tooling is where you install `.github/copilot-instructions.md` and companion files that shape how Copilot behaves in the repository.
How it compares
Use instead of hand-writing a minimal copilot-instructions stub without stack-specific sections or Actions-aware setup steps.
Common Questions / FAQ
Who is github-copilot-starter for?
Developers creating a new GitHub repository who want Copilot and optional GitHub Actions coding-agent setup generated from their language, framework, and project type.
When should I use github-copilot-starter?
Early in Build, before heavy feature work, when you can still define Copilot instructions and related `.github` config for the whole repo.
Is github-copilot-starter safe to install?
Check the Security Audits panel on this page; review any generated workflow YAML and secrets usage before enabling Actions in production orgs.
SKILL.md
READMESKILL.md - Github Copilot Starter
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: 1. **Primary Language/Framework**: (e.g., JavaScript/React, Python/Django, Java/Spring Boot, etc.) 2. **Project Type**: (e.g., web app, API, mobile app, desktop app, library, etc.) 3. **Additional Technologies**: (e.g., database, cloud provider, testing frameworks, etc.) 4. **Development Style**: (strict standards, flexible, specific patterns) 5. **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: ```md # {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 guidelines - `testing.instructions.md` - Testing standards and practices - `documentation.instructions.md` - Documentation requirements - `security.instructions.md` - Security best practices - `performance.instructions.md` - Performance optimization guidelines - `code-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 creation - `write-tests/SKILL.md` - Test generation - `code-review/SKILL.md` - Code review assistance - `refactor-code/SKILL.md` - Code refactoring - `generate-docs/SKILL.md` - Documentation generation - `debug-issue/SKILL.md` - Debugging assistance ### 4. `.github/agents/` Directory Always create these 4 agents: - `software-engineer.agent.md` - `architect.agent.md` - `reviewer.agent.md` - `debugger.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: ```markdown <!-- 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_