agentleFS
ainullmainullm/agent-checkpoint/adapters/copilot-instructions.md

agent-checkpoint / adapters

Copilot instructions3 starsChanged 39 days agoMITView on GitHub

Always adhere to the Agent-Checkpoint v2.0 protocol: - Pre-Edit Bucketing: Copy the pre-edit file into .snapshots/<filepath>/v<OLD_VERSION>.<ext>. - Sliding Window Retention: Retain maximum 5 latest versions per file bucket. - SemVer Impact: Mark change as MAJOR (structural shift), MINOR (additive feature), or PATCH (refinement/fix). - Dual-Ledger Trail: Maintain sharded index at .snapshots/<filepath>/manifest.json and append 1 line to REVISION_LOG.md table without reading old history. - Safety: Exclude heavy binaries, models, datasets > 1 MB, and dependencies.

The file

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

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Always adhere to the Agent-Checkpoint v2.0 protocol:

    line 4

≈ “Common” is an estimate: at least 1 in 5 of the 3,827 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

AGENT-CHECKPOINT PROTOCOL v2.0 (GitHub Copilot)

Place this file at .github/copilot-instructions.md

Always adhere to the Agent-Checkpoint v2.0 protocol:

  • Pre-Edit Bucketing: Copy the pre-edit file into .snapshots/<filepath>/v<OLD_VERSION>.<ext>.
  • Sliding Window Retention: Retain maximum 5 latest versions per file bucket.
  • SemVer Impact: Mark change as MAJOR (structural shift), MINOR (additive feature), or PATCH (refinement/fix).
  • Dual-Ledger Trail: Maintain sharded index at .snapshots/<filepath>/manifest.json and append 1 line to REVISION_LOG.md table without reading old history.
  • Safety: Exclude heavy binaries, models, datasets > 1 MB, and dependencies.

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.