Open full size ↗
Open full size ↗
Open a pull request from Review. QualityLayer follows its checks and comments; you control the merge.
Open full size ↗
Open full size ↗
Example task in a fictional project.
Following it
While the App is open, Review reads checks and reviewers through gh. Without it, the task stays open until a pull or fetch brings the merge to local Git, or you mark it merged.
Your agent watches the checks
The agent runs qualitylayer pr watch until the checks pass:
| Result | What your agent does |
|---|---|
| The checks pass | Checks open review threads and reads new comments. Asks you before changing anything they request |
| A check fails | Reads the log, fixes the cause, pushes, watches again. Never weakens or skips a check |
| The branch conflicts | Merges or rebases the way your repository does, checks that no commit was lost, then pushes |
| Three attempts used | Reports what still fails and stops |
It never force-pushes commits that are not its own.
When something waits for you
Open full size ↗
Open full size ↗
Failing checks, review threads and conflicts appear in Needs you while the App is open. Watch pull requests can wake or resume your agent, also for reviewers' new comments. To handle them:
- Ask your agent: “Using QL, review task retry-webhooks”, naming your actual task.
- Your agent checks the code and approved Plan, then fixes routine requests test first. Scope or design changes and replies ready to post come to you.
- Press Push the fix. Your answers post on GitHub in your name.
For review threads, pushing the fix and replying to reviewers stay yours, and so does merging.
Merged or closed
When you merge, the task moves to Shipped with what it cost. A squash or rebase merge is recognized too, and Mark as merged covers any other case. Its documents stay in docs/plans/. Further work starts with Start a follow-up.