Skip to content

Latest commit

 

History

History
40 lines (38 loc) · 2.64 KB

AGENTS.md

File metadata and controls

40 lines (38 loc) · 2.64 KB

Maintaining this marketplace

This repository is a GitHub Copilot plugin marketplace, maintained by editing its files directly. README.md shows the steps.

  • Keep documentation README-first. Every page under docs/ must have a direct, descriptive README link and only expand a topic already introduced there.
  • Each local plugin lives in plugins/<name>/ with plugin.json, README.md, and CHANGELOG.md. It's listed in marketplace.json with the same name, version, and description. Keep each plugin self-contained and installable on its own. Don't add repository settings that install or turn on plugins; people install only the plugins they want.
  • Changes under plugins/<name>/ since a known released base need a semver bump in plugin.json and marketplace.json and a matching changelog heading. An unreleased first version, including template customization, keeps its initial version and adds to its existing changelog entry. Don't bump twice, lower versions, or rewrite version history. Ask for the released base or confirmation of first-release status if missing; don't guess from a PR or the presence of a plugin on the base branch.
  • When you add or remove a plugin, update the catalog and the README's plugin table and install commands together.
  • In supported hosts after checkout trust, .github/copilot/settings.json turns on only this repository's own maintenance plugins, marketplace-maintainer and plugin-authoring, for people working here. Never add other plugins to it.
  • Remote plugins pin a full 40-character commit sha and name their ref.
  • A plugin's evals and fixtures live in evals/<name>/, outside the plugin, mirroring its folders. A skill's custom grader sits next to its eval as grader.mjs. Files several plugins share live in evals/_shared/: grader helpers in evals/_shared/graders/ and fixtures in evals/_shared/fixtures/. _shared can't collide with a plugin because plugin names start with a lowercase letter or digit. Use only synthetic data.
  • npm run lint checks skills and eval files and never calls a model. CI also validates each plugin.json against the Agent Plugins schema, matches local catalog entries to their plugin.json, and checks remote pins. npm run eval and the evals workflow run real Copilot sessions and spend AI credits; don't run them unless the user asks.
  • Use the plugin-authoring and marketplace-maintainer skills and the read-only plugin-reviewer agent when they fit the task.
  • Keep secrets and token-bearing URLs out of files. Don't commit, push, publish, change visibility, or change GitHub permissions unless the user asks.