메뉴
Set up complete GitHub Copilot configuration for a new project based on technology stack
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/muhammedadnank/Antigravity-Skills --skill github-copilot-starter명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | github-copilot-starter |
| description | Set up complete GitHub Copilot configuration for a new project based on technology stack |
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.
Ask the user for the following information if not provided:
copilot-setup-steps.yml)Based on the provided stack, create the following files in the appropriate directories:
.github/copilot-instructions.mdMain 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
Describe PR conventions, branch naming, and commit style
Reference specific instruction files for detailed standards:
Language guidelines:
Testing:
Security:
Documentation:
Performance:
Code review:
.github/instructions/ DirectoryCreate 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.github/skills/ DirectoryCreate 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.github/agents/ DirectoryAlways create these 4 agents:
software-engineer.agent.mdarchitect.agent.mdreviewer.agent.mddebugger.agent.mdFor 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 -->
.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 setupCRITICAL: The workflow MUST follow this exact structure:
copilot-setup-stepsFor each file, follow these principles:
MANDATORY FIRST STEP: Always use the fetch tool to research existing patterns before creating any content:
Primary Approach: Reference and adapt existing instructions from awesome-copilot repository:
Attribution Format: When using content from awesome-copilot, add this comment at the top of the file:
<!-- Based on/Inspired by: https://github.com/github/awesome-copilot/blob/main/instructions/[filename].instructions.md -->
Examples:
<!-- Based on: https://github.com/github/awesome-copilot/blob/main/instructions/react.instructions.md -->
---
applyTo: "**/*.jsx,**/*.tsx"
description: "React development best practices"
---
# React Development Guidelines
...
<!-- Inspired by: https://github.com/github/awesome-copilot/blob/main/instructions/java.instructions.md -->
<!-- and: https://github.com/github/awesome-copilot/blob/main/instructions/spring-boot.instructions.md -->
---
applyTo: "**/*.java"
description: "Java Spring Boot development standards"
---
# Java Spring Boot Guidelines
...
Secondary Approach: If no awesome-copilot instructions exist, create SIMPLE GUIDELINES ONLY:
STRICTLY AVOID in .instructions.md files:
CORRECT .instructions.md content:
Research Strategy with fetch tool:
Fetch these awesome-copilot directories:
Awesome-Copilot Areas to Check:
Ensure all files follow these conventions:
project-root/
├── .github/
│ ├── copilot-instructions.md
│ ├── instructions/
│ │ ├── [language].instructions.md
│ │ ├── testing.instructions.md
│ │ ├── documentation.instructions.md
│ │ ├── security.instructions.md
│ │ ├── performance.instructions.md
│ │ └── code-review.instructions.md
│ ├── skills/
│ │ ├── setup-component/
│ │ │ └── SKILL.md
│ │ ├── write-tests/
│ │ │ └── SKILL.md
│ │ ├── code-review/
│ │ │ └── SKILL.md
│ │ ├── refactor-code/
│ │ │ └── SKILL.md
│ │ ├── generate-docs/
│ │ │ └── SKILL.md
│ │ └── debug-issue/
│ │ └── SKILL.md
│ ├── agents/
│ │ ├── software-engineer.agent.md
│ │ ├── architect.agent.md
│ │ ├── reviewer.agent.md
│ │ └── debugger.agent.md
│ └── workflows/ # only if GitHub Actions is used
│ └── copilot-setup-steps.yml
Use this structure for all files:
Instructions (.instructions.md):
---
applyTo: "**/*.{lang-ext}"
description: "Development standards for {Language}"
---
# {Language} coding standards
Apply the repository-wide guidance from `../copilot-instructions.md` to all code.
## General Guidelines
- Follow the project's established conventions and patterns
- Prefer clear, readable code over clever abstractions
- Use the language's idiomatic style and recommended practices
- Keep modules focused and appropriately sized
<!-- Adapt the sections below to match the project's specific technology choices and preferences -->
Skills (SKILL.md):
---
name: github-copilot-starter
description: {Brief description of what this skill does}
---
# {Skill Name}
{One sentence describing what this skill does. Always follow the repository's established patterns.}
Ask for {required inputs} if not provided.
## Requirements
- Use the existing design system and repository conventions
- Follow the project's established patterns and style
- Adapt to the specific technology choices of this stack
- Reuse existing validation and documentation patterns
Agents (.agent.md):
---
description: Generate an implementation plan for new features or refactoring existing code.
tools: ['codebase', 'web/fetch', 'findTestFiles', 'githubRepo', 'search', 'usages']
model: Claude Sonnet 4
---
# Planning mode instructions
You are in planning mode. Your task is to generate an implementation plan for a new feature or for refactoring existing code.
Don't make any code edits, just generate a plan.
The plan consists of a Markdown document that describes the implementation plan, including the following sections:
* Overview: A brief description of the feature or refactoring task.
* Requirements: A list of requirements for the feature or refactoring task.
* Implementation Steps: A detailed list of steps to implement the feature or refactoring task.
* Testing: A list of tests that need to be implemented to verify the feature or refactoring task.
copilot-setup-steps.yml) — skip if user does not use GitHub ActionsAfter creating all files, provide the user with:
Before completing, verify:
The copilot-setup-steps.yml workflow MUST follow this exact format and KEEP IT SIMPLE:
name: github-copilot-starter Setup Steps"
on:
workflow_dispatch:
push:
paths:
- .github/workflows/copilot-setup-steps.yml
pull_request:
paths:
- .github/workflows/copilot-setup-steps.yml
jobs:
# The job MUST be called `copilot-setup-steps` or it will not be picked up by Copilot.
copilot-setup-steps:
runs-on: ubuntu-latest
permissions:
contents: read
steps:
- name: Checkout code
uses: actions/checkout@v5
# Add ONLY basic technology-specific setup steps here
KEEP WORKFLOWS SIMPLE - Only include essential steps:
Node.js/JavaScript:
- name: Set up Node.js
uses: actions/setup-node@v4
with:
node-version: "20"
cache: "npm"
- name: Install dependencies
run: npm ci
- name: Run linter
run: npm run lint
- name: Run tests
run: npm test
Python:
- name: Set up Python
uses: actions/setup-python@v4
with:
python-version: "3.11"
- name: Install dependencies
run: pip install -r requirements.txt
- name: Run linter
run: flake8 .
- name: Run tests
run: pytest
Java:
- name: Set up JDK
uses: actions/setup-java@v4
with:
java-version: "17"
distribution: "temurin"
- name: Build with Maven
run: mvn compile
- name: Run tests
run: mvn test
AVOID in workflows:
INCLUDE only: