| name | linear-sync |
| description | Turn audit and review findings into Linear issues in the right project, and define how builder agents pull work from Linear and keep building until the backlog is empty. Use when the user asks to send findings to Linear, sync tasks, or kick off autonomous building from Linear. |
| version | 1.0.0 |
| metadata | {"hermes":{"tags":["linear","tasks","sync","automation"],"category":"launch"}} |
Linear Sync
When to Use
The user wants findings to become tracked work in Linear automatically, and wants agents to work through that backlog. Trigger on "push to Linear", "sync to Linear", "send these to my board", or as the hand-off step of /ship-it.
Prerequisites
The Linear connector/MCP must be connected (hermes MCP config) with access to the target workspace. GitHub and the hosting (Vercel) connectors should also be connected so status can round-trip.
Procedure
Push (findings → Linear)
- Read the latest
.hermes/audits/audit-*.md and review-*.md.
- Map findings to the correct Linear PROJECT (match by product name; if ambiguous, ask the user once and remember the mapping in memory for next time).
- For each finding create one Linear issue using the connected Linear tools:
- Title: short and concrete.
- Description: what, where (file/URL), why it matters, suggested fix — copied from the finding.
