Skip to content
Lazurio Documentation

Lesson 8: Review and Publication

In this lesson: how to check what an agent saved and how Publication works.

Open the link from the handoff. If the page does not open, check that you are signed in to GitHub with the account you connected in Getting started. A pull request has a description and, in the tab Files changed, the exact change. Read the change itself, not only the agent’s summary, and check that:

  • it is in the right place and says what you meant;
  • every fact has a source and nothing is invented: polished text with nothing behind it goes back to the agent;
  • it contains no private data and nothing from another Organization;
  • a new colleague would understand it.

If something is wrong, say so in the same Chat thread, concretely: “Remove the deadline; the source does not confirm it.” The agent adds the fix to the same pull request or issue. You and your colleagues can also comment on GitHub.

Publication

Section titled “Publication”

Publication is the step that makes work hard to take back or visible to others: merging a pull request, sending an email or a message, submitting a form, a payment. Until then the work is a draft that can still change or be discarded. The agent publishes only when you allow it: when you choose Publish in your name in its closing question, write “publish”, or allow it in advance for a task or a whole thread. Your last word applies.

Your live rights on GitHub decide whether a merge may happen. If you may not merge, or you want someone else to check the work, choose Ask another Kolega: the agent requests that colleague’s review, assigns the pull request to them and mentions them on GitHub. In a Team Environment the agent asks instead whom it should hand the change to.

When you allow Publication, the agent’s instructions require it to merge the exact latest version of the pull request, and GitHub refuses that merge if another change has arrived in the meantime. So check the latest version before you allow it. The rule that agents publish only with your consent lives in their instructions; GitHub enforces merge rules such as required reviews only on protected branches.

Your task

Section titled “Your task”
  1. Read the change from lesson 7 in Files changed, or read the issue.
  2. Ask for at least one concrete improvement and check that it appears in the same pull request or issue.
  3. For a pull request, answer the closing question. If you are not sure that the decision is yours, choose Ask another Kolega. For an issue, check that it names who can make the change.

Done means: you have read the change itself, your feedback is in it, and you have answered the closing question or know who decides on the issue. Your first task is saved and reviewed.