Reviewing and merging
Lyra reviews every post before you see it, then tags you to merge. Your part is short: read the pull request, check the score, and merge when it is ready. Nothing publishes until you do.
This page covers reading a review, merging, handling conflicts, and deciding what to do with a post that did not clear review.
When a post is ready
A post reaches Ready when it passes review with no outstanding issues. Ready posts appear in three places:
- The Needs you queue on Overview, with a Merge button.
- The Ready filter in Blogs.
- The Ready count in the Current pipeline panel.
Read the review
Open the blog detail page and look at the reviewer panel. It shows:
- A headline score out of 100 and a verdict: Pass, Needs minor work, or Needs work.
- Scores by category: Content, SEO, AEO, E-E-A-T, Accuracy, Readability, Linking, and Voice.
- A list of issues with severity: high, medium, or low.
For a full explanation of the categories and thresholds, see Review scores.
Merge the post
You can merge from inside Lyra or on GitHub:
- In Lyra, click Merge in the Needs you queue or Merge PR #N on the blog detail page.
- On GitHub, click View on GitHub and merge the pull request there.
A merged post moves to Released, Lyra's count of posts shipped.
Read the fact verification summary
Every pull request ends with a fact verification summary: how many claims Lyra checked and confirmed, and what she corrected, dropped, or left for you to decide on. On the post in Lyra, the fact check panel lists each claim with its finding:
- Not confirmed means she could not find the claim on the page it cites and left it in for you to check.
- Contradicted means she read the page and it says something else. That is the only finding that takes a sentence out of a post.
See Review scores for how the fact check works.
Pull request states
The blog detail page shows the current state of the PR, so you know what to do next:
| State | Meaning |
|---|---|
| Merged | The post is shipped |
| Open, ready to merge | Passed review; merge when you are ready |
| Open, in review | Still being scored and fact-checked |
| Open, merge conflict | The branch conflicts with your repo; Lyra is trying to resolve it |
| Conflict, needs a human | Lyra could not resolve the conflict; fix it on GitHub, then press Merge again |
| No PR yet | The draft branch exists but the PR is not open |
Resolve conflicts
If a post's branch conflicts with your repository, Lyra tries to resolve it herself. When she cannot, the post keeps its place and its Merge button, and says in plain words what is wrong:
- A real conflict. The post points you to its pull request on GitHub. Resolve the conflict there against your default branch, then press Merge in Lyra again.
- A merge that did not finish. If the branch was never the problem, the post says so and asks you to try Merge again.
A conflict warning clears itself the moment the branch can merge, whether you fixed it or Lyra did. Once she has read a conflict she cannot resolve, she stops, says it once, and waits, so it does not cost you a writing run every few minutes. Conflicts usually happen when your blog directory changed after Lyra opened the PR.
If you merge a pull request yourself on GitHub, Lyra notices, whatever state the post was in, and moves it to Released.
When a post does not clear review
Sometimes Lyra cannot get a post past her own review bar, or a claim the post rests on cannot be confirmed. She does not call it ready. She opens the pull request as a draft, moves the post to Needs human, and offers Decide what's next on the blog detail page. The dialog explains what happened and gives you two choices:
- Keep improving buys one more writing pass at the same post, on the same pull request, using your Claude key. Click it again to buy exactly one more. For a post held back over an unconfirmed claim, it has Lyra re-source the claim or make the point without it.
- Good enough, publish it takes the pull request out of draft and moves the post to ready to merge. Nothing goes live until you press Merge, and Lyra notes on the pull request that you overrode her review.
Under Or throw this attempt away, you can also Start over or cancel the post.
If a post is finished but GitHub would not take its pull request out of draft, the dialog says so. Good enough, publish it tries that again, and is the one to use.
Stop or restart a post
- Stop kills a live run on a post.
- Retry or Write now starts it again.
- Start over discards the draft, closes the PR, and rewrites from scratch. See Writing posts.
What's next
- Ask for changes: Comment on a finished post before you merge.
- Review scores: Read the panel in depth.
- The pipeline: Where review and merge sit in the flow.
- Activity and run logs: Trace a conflict or failure.
- Analytics: See how released posts perform.