** Canonical 생태계의 GitHub Copilot에 대한 중앙화된 컨텍스트 관리.**

이 저장소는 표준화 된 Copilot Custom Instructions, Prompts, Agents 및 Skills를 배포하기 위해 "Toolkit"로 작용합니다. 개별 저장소를 "subscribe"를 특정 자산 (예, Python 표준, Juju/Ops Framework 패턴)로 설정하고 동기화된 자동을 유지합니다.

** 컬렉션은 무엇입니까? **

ACollection는 collections.yaml.]에서 정의된 markdown 파일(instructions, prompts, Agent, Skill)의 논리 그룹입니다.

50개의 다른 저장소로 특정한 지시를 수동으로 복사하는 대신, consuming 저장소는 그것을 필요로 하는 수집을 목록으로 만드는 윤곽 파일을 정의합니다.

**Available 컬렉션 (예 : **

• 핵심: 모든 저장소에 일반적인 핵심 자산.
• common-python: 표준 파이썬 코딩 스타일.
• 일반 문서: 검토 기술 문서 표준.
• charm-python: Common-python + Juju Ops Framework 특성 포함.
• copilot-toolkit : Copilot 자산 (시약, 기술, 프롬프트, 지침)을 생성하고 관리하기위한 Meta-tools.
• pfe-charms : 플랫폼 엔지니어링 특정 컬렉션.

**사용: 저장소에 추가 **

Canonical Copilot Collections

Centralized context management for GitHub Copilot across the Canonical ecosystem.

This repository acts as a “Toolkit” to distribute standardized Copilot Custom Instructions, Prompts, Agents and Skills. It allows individual repositories to “subscribe” to specific sets of assets (e.g., Python standards, Juju/Ops Framework patterns) and keep them synchronized automatically.

What are Collections?

A Collection is a logical group of markdown files (instructions, prompts, agents, and skills) defined in collections.yaml.

Instead of copying specific instructions into 50 different repositories manually, the consuming repository defines a configuration file listing the collections it needs.

Available Collections (Examples):

• core: Core assets common to all repositories.
• common-python: Standard Python coding style.
• common-documentation: Documentation standards with review skill.
• charm-python: Includes common-python + Juju Ops Framework specifics.
• copilot-toolkit: Meta-tools for generating and managing Copilot assets (agents, skills, prompts, instructions).
• pfe-charms: Platform Engineering specific collection.

Usage: Adding to a Repository

To add Copilot collections to your repository, follow these three steps.

Note: These steps assume that if the yq tool is already installed, it was installed via snap not via apt. The install scripts rely on behavior from the snap version of yq. The apt offering of yq doesn’t have the behavior the scripts expect, and will fail. If yq is not installed, the script will automatically install it via snap.

1. Create the Configuration

Create a file named .copilot-collections.yaml in the .github folder of your repository (recommended) or in the repository root.

copilot:
  # The version of the toolkit to use (matches a Release Tag in this repo)
  version: "v1.0.0"

  # The collections you want to install
  collections:
    - charm-python
    - pfe-charms

Location Preference: The workflow and sync script will search for the config file in this order:

1. .github/.copilot-collections.yaml (recommended)
2. .copilot-collections.yaml (root, for backwards compatibility)

You can also specify a custom location - see below for details.

2. Run the Initial Sync (Local)

You can sync the instructions immediately to your local machine to verify them.

curl -sL https://raw.githubusercontent.com/canonical/copilot-collections/main/scripts/local_sync.sh | bash

To specify a custom config file location:

# Via command-line argument
curl -sL https://raw.githubusercontent.com/canonical/copilot-collections/main/scripts/local_sync.sh | bash -s -- custom/path/.copilot-collections.yaml

# Via environment variable