Onboard a repo

GitHub Copilot

Copilot code review and chat read the rendered instruction files — one core file plus one scoped file per stack in the repo's profile.

What gets rendered

rendered artifacts
.github/copilot-instructions.md              # core standard, always read
.github/instructions/redline-react.instructions.md # per stack, scoped by applyTo:
.github/instructions/redline-javascript.instructions.md

Stack files carry an applyTo: frontmatter glob list, so React rules fire on **/*.tsx and never on a Go file. The redline- prefix is what makes safe pruning possible — a team's own instruction files are never touched by sync.

Connect it

  1. Onboard the repo: npx redlinegate init — the pull request it opens adds the instruction files.
  2. Enable Copilot code review for the repo or org (Copilot settings → code review).
  3. The branch ruleset ships with automatic_copilot_code_review_enabled — every PR gets reviewed without being requested.
  4. Merge the pull request. Findings arrive as review comments with the Redline/<SEVERITY> [<rule-id>]: prefix.
ℹ

The renderer that produces these files now lives inside the CLI (cli/render/vendors.ts), invoked by redline init — there is no longer a standalone script to run it against an arbitrary output directory. Copilot reads the core file plus every matching instructions file, so individual stack files stay focused. The automatic_copilot_code_review_enabled ruleset flag is the only Copilot-specific line in the entire enforcement layer.