@manuelvanrijn/opencode-copilot-instructions

An OpenCode plugin that loads .github/instructions/ files into the AI agent's system prompt — following the same applyTo: convention as GitHub Copilot custom instructions.

How it works

• Files with applyTo: are injected on-demand when the agent reads, edits, or writes a file matching the glob pattern
• Files without applyTo: are always injected at the start of every session

This means you can keep your existing .github/instructions/ setup and it works in both Copilot and OpenCode without any duplication.

Installation

opencode plugin @manuelvanrijn/[email protected] --global

Or add it to your opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["@manuelvanrijn/[email protected]"]
}

Instruction file format

Same format as GitHub Copilot — YAML frontmatter with applyTo::

---
applyTo: "app/controllers/**"
---
# Controllers Guide

Your instructions here...

Multiple globs (comma-separated):

---
applyTo: "app/models/**, test/**"
---
# Models

No frontmatter = always active:

# General Rails Guidelines

Always use...

Debugging

Enable verbose logging:

COPILOT_INSTRUCTIONS_DEBUG=1 opencode

Tool: list_injected_copilot_instructions

The plugin exposes a tool the agent can call to report the current injection status:

list_injected_copilot_instructions

Output shows which files are injected, which are pending, and which file paths have been seen in the session.

Releasing

Publishing to npm is fully automated via .github/workflows/publish.yml, triggered by pushing a v*.*.* tag.

Use the release script from a clean main:

git switch main && git pull
./scripts/release.sh patch   # or: minor | major

The script:

1. Verifies the working tree is clean.
2. Bumps the version in package.json (npm version --no-git-tag-version).
3. Updates CHANGELOG.md: renames ## Unreleased to ## vX.Y.Z — YYYY-MM-DD and adds a fresh ## Unreleased section at the top.
4. Commits (chore: release vX.Y.Z), creates tag vX.Y.Z, and pushes both to origin/main.

The tag push then triggers the GitHub Actions workflow, which:

1. Verifies the tag matches package.json version.
2. Creates a GitHub Release with auto-generated notes.
3. Publishes to npm with --provenance (OIDC / sigstore).

License

MIT