لم تُترجم هذه الصفحة بعد.

Copy an instruction and offer changes back

This page is for anyone who wants to change an instruction they don't keep, and for the maintainers who review those changes: you make your own copy, change it, and offer the changes back.

Before you start

  • An account: sign in to fork. Without an account, Fork makes a plain copy in your browser, with no link back and nothing to offer.
  • Read access: you can fork any instruction you can read, including public ones in Explore.
  • A workspace you can edit: the copy goes into the workspace you are in.
  • To review offered changes: the Maintainer role on the original. People and roles.

Fork: your own copy that keeps its origin

A fork is a copy that belongs to you and remembers where it came from. You can change it, publish it and connect agents to it, without touching the original.

  1. Open the instruction

    Open the instruction you want to copy.

  2. Fork it

    Click Share, then under Make it yours, click Fork — a copy of your own.

    If you only see an instruction's summary, because you can read its versions but not open it, click Fork it in that dialog. In the dialog that asks for access, Fork instead does the same.

  3. Start working on your copy

    The copy opens. A message says "Forked — "…" is yours to change". Next to its name, the header shows Copy of …, a link back to the original.

The copy starts from the live version of the original, the version its readers get. If the original has never been published, and you can read its draft, the copy starts from the draft. It keeps the original's licence. Who can read your copy follows your organization's default, or Only you when it has none.

When you can't fork

What you see Why
"its owner doesn't allow forks of this instruction" Its owner turned forks off. People who manage it can still fork it.
"sealed instructions can't be forked on the platform" It is in a sealed workspace, which instruction.md can't read.
"it has no released version to fork yet" Nothing is published yet, and you can't read its draft.
"sign in to fork" Sign in first.

Offer changes

When your copy is ready, offer it back. The original's maintainers see your whole text next to the version you started from.

  1. Open your copy

    Open your fork. In its header, next to Share, there is an Offer changes button.

  2. Say what and why

    Click Offer changes. The dialog Offer your changes back to "…" asks two things:

    • What it changes: one line, for example "Refunds over €150 need a manager".
    • Why: what its maintainers should know. This is optional.
  3. Send it

    Click Offer it.

    A message says "Offered — its maintainers are told, and you'll hear what they decide".

Offer your copy's text back to the original's maintainers.

What is offered is your copy's text as it is now. Suggestions waiting on your copy aren't part of it until you accept them.

Follow its state on the header

After you offer, the header button shows where your offer stands:

  • Offered · waiting for review: the maintainers haven't decided yet.
  • Offered · approved: a maintainer approved it. It becomes a version when they merge it.
  • Offered · changes asked for: a maintainer asked you to change something. The button is highlighted.

You get a notification each time a maintainer approves it, asks for changes or closes it.

Update or withdraw your offer

Click the header button to open Your offer. It says where the offer stands and what the maintainer said.

  • To send a new text, change your copy first, then click Send my changes again. Your offer is based on the newest version of the original again, and a maintainer can review it again.
  • To take it back, click Withdraw it. The maintainers are told.

Review offered changes

  1. Open the offered changes

    You get a notification when someone offers changes. Open it, or open the instruction, click Search in the side bar (or press Ctrl+K, ⌘K on a Mac), and pick Offered changes….

    The dialog Offered to "…" lists every offer not settled yet. Each shows its line, who offered it, the version it started from, its state, and why.

  2. Compare

    Click Compare. The version it started from and the offered text open side by side.

    If the offer says out of date: the instruction moved on, a version was published after it started. See the warning below.

  3. Decide

    • Approve: you agree with it. You can't approve your own offer.
    • Request changes: write what should change in What should change, then click Send. Its author is told, and it can't be merged until they send it again.
    • Merge: publish it as a new version. See the next step.
    • Close: it isn't taken. A question asks you first, and its author is told. Their copy stays theirs.
  4. Merge it

    Click Merge. A question asks, for example, "Merge "Refunds over €150 need a manager" as v6 of Refund policy?". It says how many agents that follow the live version switch to it, and that the draft's own changes stay in the draft.

    Click Merge it. A message says "Merged — v6 is made from it". v6 is live, and the agents that follow the live version switch to it.

Review it inside Claude or ChatGPT

If you connected Claude or ChatGPT to instruction.md, you can review there too. Ask it, for example, "Show me the changes offered to Refund policy". It opens a review view in the conversation: the offer's line, who offered it, and what it changes, line by line.

The buttons there are Approve, Request changes, Merge and publish once it is approved, Close and Reject. When it is out of date, its author sees Rebase, which moves the offer onto the newest version. You can add a Review comment first. Before it merges, the view asks you to Confirm. If you offered the changes yourself, it says "Authors do not review their own proposals; a reviewer with publish permission approves and merges."

Review offered changes without leaving Claude.

See Connect Claude or ChatGPT.

Suggestions, comments and offered changes

A suggestion A comment Offered changes
What it is A change to a few words of the draft, marked in the text A note on a part of the text, with replies A whole new text, from your own copy
Who makes it A Contributor, or anyone who chooses to suggest Contributors and maintainers Anyone who can read the instruction
Where it lives In the original's draft In the original's draft Your text stays in your fork; the offer waits on the original
Who decides A maintainer accepts or rejects it Anyone can reply; it is resolved when done A maintainer approves, merges or closes it
What it becomes Part of the draft, published with the next version Nothing: it never reaches agents A new version as soon as it is merged

Use a suggestion for a small change when you can work on the instruction itself. Use offered changes when you can't, or when you want to try a larger change in your own copy first. See Suggest changes and review them.

Check it worked

  • On your fork, the header shows Offered · waiting for review.
  • On the original, Offered changes… lists your offer.
  • After a merge, the original's History shows the new version marked Live.

Undo or stop

  • Withdraw it, in Your offer, takes back an offer.
  • A merged offer is a version like any other. To undo it, make the version before it live again. See Roll back or withdraw a version.
  • Your fork stays yours whatever the maintainers decide. Delete it like any other instruction when you no longer need it.

If it doesn't work

What you see What to do
"Say in a line what it changes, then offer it" Fill in What it changes.
"this text is the same as the latest version" Your copy has no changes yet. Change it first.
"Nothing new to send: change your copy first, then send it again" You sent the same text again. Change your copy first.
"you have 10 proposals open on this instruction; close one, or wait for its maintainers" You can have 10 offers waiting on one instruction. Withdraw one, or wait for answers.
"it is archived and takes no proposals" The original is archived. Ask its owner.
"changes were asked for; its author updates it first" Wait until its author sends it again, then merge.

Still stuck: Troubleshooting.

Questions

What is the difference between a suggestion, a comment and offered changes?

A suggestion changes a few words in the instruction's own draft, and a maintainer accepts or rejects it. A comment is a note that never reaches agents. Offered changes are a whole text from your own copy, which a maintainer merges as a new version. The table.

Does my fork follow the original's new versions?

No. Your fork is a separate instruction from the moment you make it. It keeps a link back to the original, but new versions of the original don't change it.

Who sees what I offer?

The original's maintainers, and anyone who can read its draft. They see your line, your reason, and your whole text. Its maintainers decide whether it becomes a new version.

Do agents get my changes when I offer them?

No. Agents get them only after a maintainer merges your offer, which publishes it as a new version.

For developers: the tools behind forks and offers, and the review view.

Last checked against the product:

Was this page helpful? Report a problem