RonanCodes/linear-nightshift
skills/linear-nightshift/SKILL.md
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".
devops
Updated Jun 13, 2026
$ install --global
skillsauthnpx skillsauth add RonanCodes/ronan-skills linear-nightshiftInstall 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 13, 2026, 2:29 AM82.3s1 file scanned
SKILL.md
- name:
- linear-nightshift
- description:
- 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".
- category:
- workflow
- argument-hint:
- --team <KEY> --repo <owner/name> [--collaborator <name>] [--workers N] [--plan-only]
- allowed-tools:
- Bash Read Write Agent
/ro:linear-nightshift
The hybrid one-way sync in motion (model locked 2026-06-11, ronan-skills#61): Linear is where collaborator stories are born and prioritised; GitHub is the execution layer. This skill is the bridge — it never makes Linear a second execution tracker and never makes the collaborator touch GitHub.
Collaborator files story (Backlog or Ready for agent)
→ /ro:linear-grill asks questions (state: Question for <name>)
→ collaborator answers in comments ← their only job
→ next /ro:linear-grill run promotes to Grilled
→ THIS SKILL: verify answers → mirror to GH → night-shift drains
→ /ro:linear-update marks Done with PR + try-it link
API mechanics (auth, mentions, states, complexity cap) and board resolution via the repo's .ro-linear.json: see /ro:linear-grill § "Linear API mechanics" and § "Step 0".
Step 0: Repo-mode + pre-flight
- Defer to
/ro:repo-mode:workrepos NEVER touch Linear or GH — refuse loudly. - Probe: team's Grilled issues (
state.type = unstarted, name from the repo's.ro-linear.jsonstates.grilled) + their comments; the target repo's existing queue (gh issue list --label ready-for-agent). Print a pre-flight summary: N grilled tickets, M look answered, K look unanswered, existing GH queue depth.
Step 1: Answer-verification gate (the load-bearing check)
For each Grilled ticket, find the latest grill comment (API-user comment containing numbered questions). Then judge:
- No grill comment ever → the ticket skipped grilling. Don't block on process: if the description alone is buildable, proceed; if not, grill it now (inline
/ro:linear-grill --issue <ID>) and bounce. - Collaborator replied after the grill → read their reply against each question. Enough answered to build without guessing? Proceed (note unanswered minor points as assumptions in the mirror issue). Materially unanswered? → bounce.
- No reply after the grill → bounce.
Bounce = one comment, mention-first, naming exactly which questions are open ("@name — moving this back to your questions column: questions 2 and 4 still decide the build…"), then issueUpdate state → the questions state from .ro-linear.json (e.g. "Question for Eoin"). Never silently skip — the collaborator must see WHY their ticket didn't run.
Step 2: Mirror verified tickets to GitHub
For each verified ticket, create an ephemeral execution mirror:
gh issue create --label ready-for-agent --label linear-mirror \
--title "<ticket title> (NUT-<n>)" \
--body "## Linear\n\n<ticket URL> — canonical story + the collaborator's answers.\n\n<description + distilled answers + assumptions>\n\n### Close-the-loop tests\n<standard block>"
Rules: the mirror carries the distilled answers (workers must not need Linear access); create the linear-mirror label once (idempotent, case-insensitive check); move the Linear ticket to In Progress with a one-line comment ("queued for tonight's build run").
Step 3: Run the standard night-shift
Invoke /ro:night-shift (or /ro:planner-worker --queue) against the repo's GH queue — the mirrors are ordinary ready-for-agent issues; ALL existing machinery (worktrees, dev-links, Closes #N, mergers with the stale-squash guard, retro, nightsheet, Pushover/Telegram) applies unchanged. This skill adds nothing to the execution layer.
Step 4: Tail — close the loop
After the run (and deploy, per the repo's policy): for every mirror whose PR merged, invoke /ro:linear-update --issue <NUT-n> --pr <#> --deployed. For mirrors that escalated/stuck: comment on the Linear ticket honestly (what blocked it), move back to Grilled.
Flags
--plan-only — pre-flight + verification verdicts only, no mirrors, no run. --workers N, caps: passed through to night-shift.
Errors
| Condition | Behaviour |
|---|---|
| Zero Grilled tickets | Say so; suggest /ro:linear-grill if Backlog has ungrilled tickets |
| All Grilled tickets bounce | Report each bounce reason; no run |
| Repo-mode = work | Refuse: this flow is for personal repos only |
Related
/ro:linear-grill (upstream) · /ro:linear-update (tail) · /ro:night-shift (the engine) · ronan-skills#61 (design)
Related Skills
RonanCodes/linear-update
development
VerifiedTrustedCommunity
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".
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