RonanCodes/linear-update
skills/linear-update/SKILL.md
Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
development
Updated Jun 12, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills linear-updateInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 2:30 AM124.0s1 file scanned
SKILL.md
- name:
- linear-update
- description:
- Close the loop on a Linear ticket when its work ships - move the status and post a deploy comment with the PR link, what shipped, and a try-it link, mentioning the collaborator. Used as the tail of /ro:linear-nightshift for every merged mirror, or manually after an ad-hoc build. Triggers on "linear update", "update the linear ticket", "mark NUT-x done", "tell eoin it shipped", "/ro:linear-update".
- category:
- workflow
- argument-hint:
- --issue <ID> [--pr <number>] [--state Done|"In Review"] [--deployed] [--try-url <url>] [--repo <owner/name>]
- allowed-tools:
- Bash(python3 *) Bash(curl *) Bash(gh *) Read
/ro:linear-update
The deploy-time half of the hybrid sync (ronan-skills#61): the collaborator filed the story on Linear, answered the grill, and the build ran on GitHub — this skill brings the outcome back to where THEY live, so the board is self-explanatory without ever opening GitHub.
API mechanics (auth header without Bearer, @[displayName](uuid) mentions, per-team states): see /ro:linear-grill § "Linear API mechanics".
Step 1: Resolve inputs
--issue <ID>(e.g. NUT-21) — required. Resolve to the issue id + team via a slim query.--pr <number>+--repo— fetch title, merge SHA, and the close-with-summary comment from the linked GH issue if one exists (richest source for "what shipped").--state: default Done when--deployed, else In Review (merged but not yet live — mirrors the DAFO convention: Done only when shipped).--try-url: default = the repo's production URL if known (e.g. from the README or wrangler config); omit the try-it line when unknown — never invent a URL.
Step 2: Update + comment
issueUpdate→ target state.commentCreatewith the deploy comment:
@[<displayName>](<uuid>) — **shipped and live** 🎉
**What you get:** <1-3 plain-language lines — outcome, not implementation. "Type a team in the fixture picker and pick from their upcoming games" beats "added upcoming_fixtures store">
**Try it:** <try-url, ideally deep-linked to the feature>
**Under the hood:** PR <link> (merged <sha-short>)
<If anything was assumed or descoped from their answers, one honest line about it + what would change it.>
Rules: plain language (the collaborator is not an engineer); calibrated — if it's merged-but-not-deployed, say "lands with the next deploy", don't claim live; if the build made assumptions on their unanswered questions, surface them here, not never.
Step 3: Report
Print: ticket → state, comment posted, and (when called from /ro:linear-nightshift) accumulate into the run's nightsheet line ("Linear loop closed: NUT-21, NUT-24 → Done with deploy comments").
Idempotency
Re-running on a ticket already in the target state with an existing deploy comment for the same PR: skip with "already closed for PR #N". A NEWER PR for the same ticket appends a fresh comment.
Errors
| Condition | Behaviour |
|---|---|
| Issue ID not found | List the team's recent identifiers, ask |
| --deployed but no deploy evidence (no live URL probe passes) | Post as In Review with "lands with the next deploy" instead; say why |
Related
/ro:linear-nightshift (calls this at its tail) · /ro:linear-grill (the upstream questions this answers) · ronan-skills#61 (design)
Related Skills
RonanCodes/linear-nightshift
devops
VerifiedTrustedCommunity
Run a night-shift against a collaborator's Linear board. Pulls the team's Grilled tickets (/ro:linear-grill moves a ticket to Grilled once its questions are answered), VERIFIES the questions were actually answered (unanswered → bounce the ticket to the "Question for <name>" state), mirrors verified tickets to ephemeral GitHub issues with ready-for-agent, then runs the standard /ro:night-shift machinery on GitHub. Tail-calls /ro:linear-update for everything that merged + deployed. Triggers on "linear nightshift", "nightshift linear", "drain the linear board", "run the shift off linear", "/ro:linear-nightshift".
SKILL.mdUpdated Jun 12, 2026
RonanCodes/linear-grill
development
VerifiedTrustedCommunity
Grill a collaborator's Linear tickets and move every processed ticket to where it belongs. Resolves the board from the repo's .ro-linear.json, reads the collaborator's Backlog / Ready-for-agent issues, then per ticket either posts 3-5 decision-extracting questions (state moves to "Question for <name>") or confirms it build-ready (state moves to "Grilled", the gate /ro:linear-nightshift consumes); shipped-and-confirmed tickets close as Done. The async-collaborator counterpart of /ro:day-shift for people who never touch GitHub. Triggers on "grill linear", "grill eoin's tickets", "linear grill", "add questions to the linear tickets", "/ro:linear-grill".
SKILL.mdUpdated Jun 12, 2026
RonanCodes/skills/about-page
development
VerifiedTrustedCommunity
--- name: about-page description: Add a standard About page to any web app, what it is, the tech stack, and an FAQ, wired into a footer link with a sticky footer. Built with Spartan + Tailwind (the canonical component layer) and falls back to semantic HTML so it ships reliably. Use whenever building, polishing, or shipping an app, every app should have one. Triggers on "add an about page", "about page", "footer about link", or as a standard step in app build/polish. category: frontend argument-h
SKILL.mdUpdated Jun 9, 2026
RonanCodes/waitlist-access-control
data-ai
VerifiedTrustedCommunity
Wire the common "invite-only with a waitlist" access pattern into a TanStack Start + Better Auth + Drizzle + Resend app — passwordless email-OTP sign-in gated by an email allowlist, a public waitlist capture with confirmation email, a "you're in" email when an address is whitelisted, a super-admin / admin / member role tier, and a super-admin-only admin section to view users, view the waitlist, whitelist emails, and promote admins. Use when the user wants invite-only access, an allowlist/whitelist of emails, a waitlist with emails, gated sign-up, an admin user-management section, role tiers, or "only let approved people in".
SKILL.mdUpdated Jun 8, 2026