GitHub updates, alongside your Linear issue. Ask for the next step.
Connect an issue to its pull requests, reviews and deployments. Rules check the linked work, chains keep its timeline current, and @warestack answers questions from the issue and the observed change record.
OAuth once per workspace. Install the agent separately so mentions start sessions.
orbital
Three ways to use the connected issue.
Written as GitHub events happen. Which events are written is decided per chain.
Opened, standards checked, review requested, reviewer messaged, changes requested, merged, deployed. Each with who, when and the status word.
A chain can comment on the issue instead of, or as well as, posting to Slack. Escalate-once replies in the same comment thread.
Mention the agent on the issue and it answers from the issue and the linked pull request: review state, standards, checks, deployment, next step. Delegate it a task and it reports back.
Status and next step, on the issue.
The Warestack agent runs as a Linear agent session. It reads the issue and the linked pull request, answers with its sources, and recommends the next step. It does not write code.
Grounded. Answers come from the Warestack record and the issue. Nothing is inferred from the codebase.
Delegation. Assign the agent a follow-up and it posts the result as an activity on the issue when done.
@warestack where is this and what do we do next?
Read the issue and console-web #1182. In progress, waiting on the author.
Review. Changes requested by jmarchetti on Oct 2, three threads open.
Standards. 11 of 12 passed. One finding: feat/ requires 2 human approvals, 0 counted. Not blocking.
Next step. Address the three threads and re-request review from jmarchetti.
Standards that read Linear.
They run on the pull request, where the change can still be fixed. All start informational.
Flags pull requests not linked to a Linear issue by key in the branch, title or body.
Flags pull requests whose linked issue has no assignee.
Flags pull requests whose linked issue is not in progress.
Flags pull requests whose changes do not match the linked issue’s description.
Flags pull requests on an Urgent issue with no review or acknowledgment within the time limit.
Connected in three steps.
A space admin connects once. Addresses are shared by every chain; scope belongs to the chain.
Review the current Linear scopes during connection. Warestack processes linked issue descriptions, comments and requests addressed to its agent.