agentleFS
ThibautBaissacThibautBaissac/rails_ai_agents/.github/copilot-instructions.md

rails_ai_agents

Copilot instructions665 starsChanged 6 months agoMITView on GitHub

Use these instructions as a compatibility bridge so GitHub Copilot can reuse this repo's Claude-oriented assets without duplicating them. Run both scripts after adding, removing, or renaming a rule or skill.

The file

We split this copilot-instructions.md into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use these instructions as a compatibility bridge so GitHub Copilot can reuse this repo's Claude-oriented assets without duplicating them.

    line 3
  2. Very specific:

    Follow the canonical .claude/rules/*.md content, not the bridge text.

    line 15
  3. Very specific:

    Treat .agents/skills/*/SKILL.md as Copilot-facing skills.

    line 19
  4. Very specific:

    Do not rewrite or duplicate .claude/rules/* content into .github/instructions/*.

    line 24
  5. Very specific:

    Do not manually copy .claude/skills/* into .agents/skills/*.

    line 25
  6. Distinctive:

    Keep bridges and mirrors in sync via scripts:

    line 26
  7. Distinctive:

    Run both scripts after adding, removing, or renaming a rule or skill.

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 3,854 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

GitHub Copilot Instructions

Use these instructions as a compatibility bridge so GitHub Copilot can reuse this repo's Claude-oriented assets without duplicating them.

Canonical Sources

  • Architecture and workflow conventions: AGENTS.md
  • Canonical Claude instructions and rules: .claude/
  • Copilot-friendly mirrored skills: .agents/skills/

Rule Loading Strategy

  • Path-scoped Copilot bridge files live in .github/instructions/claude-rules/.
  • Each bridge points to a canonical .claude/rules/*.md file.
  • Follow the canonical .claude/rules/*.md content, not the bridge text.

Skills Strategy

  • Treat .agents/skills/*/SKILL.md as Copilot-facing skills.
  • .claude/skills/ remains the source of truth.

Maintenance Rules

  • Do not rewrite or duplicate .claude/rules/* content into .github/instructions/*.
  • Do not manually copy .claude/skills/* into .agents/skills/*.
  • Keep bridges and mirrors in sync via scripts:
scripts/sync_claude_rules_to_copilot.sh
scripts/sync_claude_skills_to_codex.sh

Run both scripts after adding, removing, or renaming a rule or skill.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.