GitHub Copilot — Official Customization Collection
Official GitHub Copilot customization: agents, skills, instructions, plugins, hooks, and agentic workflows. Plus documentation.
Installation agent prête
Cet actif peut être installé après choix du runtime, vérification du plan et exécution de la commande adaptée.
npx -y tokrepo@latest install 1e571d3c-6269-4037-afde-db332bdab08a --target codexÀ exécuter après confirmation du plan en dry-run.
What it is
This collection gathers official GitHub Copilot customization resources including agents, skills, instruction files, plugins, hooks, and agentic workflow patterns. It covers the full spectrum of Copilot extensibility.
The collection targets developers and teams who want to move beyond default Copilot suggestions and configure it for their specific codebase, coding standards, and development workflows.
The project is actively maintained and suitable for both individual developers and teams looking to integrate it into their existing toolchain. Documentation and community support are available for onboarding.
How it saves time or tokens
Custom instructions tell Copilot about your project conventions, reducing irrelevant suggestions. Agents and skills automate multi-step workflows (code review, test generation, documentation) that would otherwise require manual prompting. Hooks integrate Copilot into CI/CD pipelines for automated code quality checks.
For teams evaluating multiple tools in the same category, the clear documentation and active community reduce the time spent on research and troubleshooting. Getting started takes minutes rather than hours of configuration.
How to use
- Browse the collection to identify customization types relevant to your workflow.
- Copy instruction files to your
.github/copilot-instructions.mdfor repository-level customization. - Install agent extensions for VS Code or JetBrains to add specialized Copilot capabilities.
- Configure hooks to trigger Copilot-powered actions on git events (pre-commit, PR open).
Example
<!-- .github/copilot-instructions.md -->
# Project Context for Copilot
Tech Stack
- Frontend: React 19 + TypeScript + TailwindCSS
- Backend: Go with Chi router
- Database: PostgreSQL with pgx driver
Coding Standards
- Use functional components with hooks, no class components
- All API responses follow { data, error, meta } envelope
- Error handling: wrap errors with fmt.Errorf, never panic
- Tests: table-driven tests for Go, React Testing Library for frontend
Related on TokRepo
- AI Tools for Coding — Compare Copilot with other AI coding assistants.
- Prompt Library — Prompt templates that work with Copilot's instruction system.
Common pitfalls
- Writing overly long instruction files that exceed Copilot's context window. Keep instructions focused on conventions that differ from defaults.
- Installing too many agent extensions at once. Each extension adds overhead. Start with one or two that address your highest-frequency workflows.
- Not testing instruction changes. After updating
.github/copilot-instructions.md, verify that Copilot's suggestions actually reflect the new instructions before rolling out to the team. - Applying the skill without reading the documentation first. Each skill has specific prerequisites and configuration requirements that affect the quality of results.
Questions fréquentes
A markdown file (`.github/copilot-instructions.md`) that provides project-specific context to Copilot. It describes your tech stack, coding conventions, and patterns so Copilot generates suggestions that match your project's style.
Copilot agents are extensions that add specialized capabilities beyond code completion. They can review PRs, generate tests, explain code, or perform multi-step development workflows using Copilot's AI backend.
Instruction files work in any IDE with Copilot support. Agent extensions are IDE-specific. Most agents are available for VS Code, with growing support for JetBrains and Neovim.
Yes. Instruction files live in your repository and apply to all team members. Agent extensions can be recommended via VS Code workspace settings or a team-shared extensions list.
Copilot customization features require an active GitHub Copilot subscription (Individual, Business, or Enterprise). The customization files themselves are free to create and share.
Sources citées (3)
- GitHub Copilot Docs— Copilot instruction files for repository-level customization
- GitHub Copilot Extensions— Copilot extensibility with agents and plugins
- GitHub Blog— Agentic coding workflows
En lien sur TokRepo
Source et remerciements
Created by GitHub. Licensed under MIT. awesome-copilot — ⭐ 27,500+ Docs: docs.github.com/copilot/customizing-copilot
Fil de discussion
Actifs similaires
FauxPilot — Self-Hosted GitHub Copilot Alternative
FauxPilot is an open-source server that provides GitHub Copilot-compatible code completion using locally hosted language models, giving teams private AI-assisted coding without sending code to external services.
lnai — Unified AI Config for Claude, Cursor, Copilot & More
Define AI tool configs once in a .ai/ directory and auto-sync to Claude Code, Cursor, GitHub Copilot, Gemini CLI, Codex, and Windsurf native formats.
Spec Kit — Spec-Driven Dev Toolkit from GitHub, 85K Stars
GitHub's open-source spec-driven development toolkit. Turn product specs into executable AI agent workflows via the specify CLI instead of vibe coding.
Llama Stack — Meta Official LLM App Framework
Official Meta framework for building LLM applications with Llama models. Inference, safety, RAG, agents, evals, and tool use. Standardized APIs. 8.3K+ stars.