PaperclipOrg
Claude Agent Skill · by Github

Github Copilot Starter

Sets up a complete GitHub Copilot configuration structure for new projects, creating instruction files, agents, skills, and workflows based on your tech stack.

Install
Terminal · npx
$npx skills add https://github.com/github/awesome-copilot --skill github-copilot-starter
Works with Paperclip

How Github Copilot Starter fits into a Paperclip company.

Github Copilot Starter drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.

S
SaaS FactoryPaired

Pre-configured AI company — 18 agents, 18 skills, one-time purchase.

$27$59
Explore pack
Source file
SKILL.md402 lines
Expand
---name: github-copilot-starterdescription: '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. ## 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 OverviewBrief description of what this project does and its primary purpose. ## Tech StackList 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/` DirectoryCreate 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/` DirectoryCreate reusable skills as self-contained folders: