github-copilot-starter

Name: github-copilot-starter
Author: github

8.8kinstalls4.6kforks

How to install github-copilot-starter?

github/awesome-copilot/github-copilot-starter

$npx -y skills add github/awesome-copilot --skill github-copilot-starter

Installs into the current project.

Summary

Set up complete GitHub Copilot configuration for a new project based on technology stack

Files · 1

View on GitHub

SKILL.md

1	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.
2
3	## Project Information Required
4
5	Ask the user for the following information if not provided:
6
7	1. Primary Language/Framework: (e.g., JavaScript/React, Python/Django, Java/Spring Boot, etc.)
8	2. Project Type: (e.g., web app, API, mobile app, desktop app, library, etc.)
9	3. Additional Technologies: (e.g., database, cloud provider, testing frameworks, etc.)
10	4. Development Style: (strict standards, flexible, specific patterns)
11	5. GitHub Actions / Coding Agent: Does the project use GitHub Actions? (yes/no — determines whether to generate `copilot-setup-steps.yml`)
12
13	## Configuration Files to Create
14
15	Based on the provided stack, create the following files in the appropriate directories:
16
17	### 1. `.github/copilot-instructions.md`
18	Main repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.
19
20	Use this structure:
21	```md
22	# {Project Name} — Copilot Instructions
23
24	## Project Overview
25	Brief description of what this project does and its primary purpose.
26
27	## Tech Stack
28	List the primary language, frameworks, and key dependencies.
29
30	## Conventions
31	- Naming: describe naming conventions for files, functions, variables
32	- Structure: describe how the codebase is organized
33	- Error handling: describe the project's approach to errors and exceptions
34
35	## Workflow
36	- Describe PR conventions, branch naming, and commit style
37	- Reference specific instruction files for detailed standards:
38	- Language guidelines: `.github/instructions/{language}.instructions.md`
39	- Testing: `.github/instructions/testing.instructions.md`
40	- Security: `.github/instructions/security.instructions.md`
41	- Documentation: `.github/instructions/documentation.instructions.md`
42	- Performance: `.github/instructions/performance.instructions.md`
43	- Code review: `.github/instructions/code-review.instructions.md`
44	```
45
46	### 2. `.github/instructions/` Directory
47	Create specific instruction files:
48	- `{primaryLanguage}.instructions.md` - Language-specific guidelines
49	- `testing.instructions.md` - Testing standards and practices
50	- `documentation.instructions.md` - Documentation requirements
51	- `security.instructions.md` - Security best practices
52	- `performance.instructions.md` - Performance optimization guidelines
53	- `code-review.instructions.md` - Code review standards and GitHub review guidelines
54
55	### 3. `.github/skills/` Directory
56	Create reusable skills as self-contained folders:
57	- `setup-component/SKILL.md` - Component/module creation
58	- `write-tests/SKILL.md` - Test generation
59	- `code-review/SKILL.md` - Code review assistance
60	- `refactor-code/SKILL.md` - Code refactoring
61	- `generate-docs/SKILL.md` - Documentation generation
62	- `debug-issue/SKILL.md` - Debugging assistance
63
64	### 4. `.github/agents/` Directory
65	Always create these 4 agents:
66	- `software-engineer.agent.md`
67	- `architect.agent.md`
68	- `reviewer.agent.md`
69	- `debugger.agent.md`
70
71	For each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.
72
73	Agent Attribution: When using content from awesome-copilot agents, add attribution comments:
74	```markdown
75	<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/agents/[filename].agent.md -->
76	```
77
78	### 5. `.github/workflows/` Directory (only if user uses GitHub Actions)
79	Skip this section entirely if the user answered "no" to GitHub Actions.
80
81	Create Coding Agent workflow file:
82	- `copilot-setup-steps.yml` - GitHub Actions workflow for Coding Agent environment setup
83
84	CRITICAL: The workflow MUST follow this exact structure:
85	- Job name MUST be `copilot-setup-steps`
86	- Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)
87	- Set appropriate permissions (minimum required)
88	- Customize steps based on the technology stack provided
89
90	## Content Guidelines
91
92	For each file, follow these principles:
93
94	MANDATORY FIRST STEP: Always use the fetch tool to research existing patterns before creating any content:
95	1. Fetch specific instruction from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md
96	2. Fetch specific agents from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md
97	3. Fetch specific skills from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md
98	4. Check for existing patterns that match the technology stack
99
100	Primary Approach: Reference and adapt existing instructions from awesome-copilot repository:
101	- Use existing content when available - don't reinvent the wheel
102	- Adapt proven patterns to t

People who liked this also viewed

6 picks

Type

hyperframes-cliUse the HyperFrames CLI development loop: init, add, catalog, capture, lint, check, snapshot, compare, grade-compare, preview, play, present, beats, keyframes, single or batch render, publish, cloud, SkillsJul 2026262k37k
request-refactor-planSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026165k181k
analyze-projectRigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrSkillsMay 2026161k507
explore-codeRigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated braSkillsMay 2026161k507
ubiquitous-languageSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026160k181k
scaffold-exercisesSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026149k181k

github-copilot-starter

8.8kinstalls4.6kforks

View on GitHub

How to install github-copilot-starter?

github/awesome-copilot/github-copilot-starter

$npx -y skills add github/awesome-copilot --skill github-copilot-starter

Installs into the current project.

Summary

Set up complete GitHub Copilot configuration for a new project based on technology stack

Files · 1

View on GitHub

SKILL.md

1	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.
2
3	## Project Information Required
4
5	Ask the user for the following information if not provided:
6
7	1. Primary Language/Framework: (e.g., JavaScript/React, Python/Django, Java/Spring Boot, etc.)
8	2. Project Type: (e.g., web app, API, mobile app, desktop app, library, etc.)
9	3. Additional Technologies: (e.g., database, cloud provider, testing frameworks, etc.)
10	4. Development Style: (strict standards, flexible, specific patterns)
11	5. GitHub Actions / Coding Agent: Does the project use GitHub Actions? (yes/no — determines whether to generate `copilot-setup-steps.yml`)
12
13	## Configuration Files to Create
14
15	Based on the provided stack, create the following files in the appropriate directories:
16
17	### 1. `.github/copilot-instructions.md`
18	Main repository instructions that apply to all Copilot interactions. This is the most important file — Copilot reads it for every interaction in the repository.
19
20	Use this structure:
21	```md
22	# {Project Name} — Copilot Instructions
23
24	## Project Overview
25	Brief description of what this project does and its primary purpose.
26
27	## Tech Stack
28	List the primary language, frameworks, and key dependencies.
29
30	## Conventions
31	- Naming: describe naming conventions for files, functions, variables
32	- Structure: describe how the codebase is organized
33	- Error handling: describe the project's approach to errors and exceptions
34
35	## Workflow
36	- Describe PR conventions, branch naming, and commit style
37	- Reference specific instruction files for detailed standards:
38	- Language guidelines: `.github/instructions/{language}.instructions.md`
39	- Testing: `.github/instructions/testing.instructions.md`
40	- Security: `.github/instructions/security.instructions.md`
41	- Documentation: `.github/instructions/documentation.instructions.md`
42	- Performance: `.github/instructions/performance.instructions.md`
43	- Code review: `.github/instructions/code-review.instructions.md`
44	```
45
46	### 2. `.github/instructions/` Directory
47	Create specific instruction files:
48	- `{primaryLanguage}.instructions.md` - Language-specific guidelines
49	- `testing.instructions.md` - Testing standards and practices
50	- `documentation.instructions.md` - Documentation requirements
51	- `security.instructions.md` - Security best practices
52	- `performance.instructions.md` - Performance optimization guidelines
53	- `code-review.instructions.md` - Code review standards and GitHub review guidelines
54
55	### 3. `.github/skills/` Directory
56	Create reusable skills as self-contained folders:
57	- `setup-component/SKILL.md` - Component/module creation
58	- `write-tests/SKILL.md` - Test generation
59	- `code-review/SKILL.md` - Code review assistance
60	- `refactor-code/SKILL.md` - Code refactoring
61	- `generate-docs/SKILL.md` - Documentation generation
62	- `debug-issue/SKILL.md` - Debugging assistance
63
64	### 4. `.github/agents/` Directory
65	Always create these 4 agents:
66	- `software-engineer.agent.md`
67	- `architect.agent.md`
68	- `reviewer.agent.md`
69	- `debugger.agent.md`
70
71	For each, fetch the most specific match from awesome-copilot agents. If none exists, use the generic template.
72
73	Agent Attribution: When using content from awesome-copilot agents, add attribution comments:
74	```markdown
75	<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/agents/[filename].agent.md -->
76	```
77
78	### 5. `.github/workflows/` Directory (only if user uses GitHub Actions)
79	Skip this section entirely if the user answered "no" to GitHub Actions.
80
81	Create Coding Agent workflow file:
82	- `copilot-setup-steps.yml` - GitHub Actions workflow for Coding Agent environment setup
83
84	CRITICAL: The workflow MUST follow this exact structure:
85	- Job name MUST be `copilot-setup-steps`
86	- Include proper triggers (workflow_dispatch, push, pull_request on the workflow file)
87	- Set appropriate permissions (minimum required)
88	- Customize steps based on the technology stack provided
89
90	## Content Guidelines
91
92	For each file, follow these principles:
93
94	MANDATORY FIRST STEP: Always use the fetch tool to research existing patterns before creating any content:
95	1. Fetch specific instruction from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md
96	2. Fetch specific agents from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.agents.md
97	3. Fetch specific skills from awesome-copilot docs: https://github.com/github/awesome-copilot/blob/main/docs/README.skills.md
98	4. Check for existing patterns that match the technology stack
99
100	Primary Approach: Reference and adapt existing instructions from awesome-copilot repository:
101	- Use existing content when available - don't reinvent the wheel
102	- Adapt proven patterns to t

People who liked this also viewed

6 picks

Type