skills/council-ship/SKILL.md
Alias for /ro:council-review --fix --ship. One gesture from dirty branch to deployed main, council review, fix loop, gate, squash-merge, deploy. When the user types /ro:council-ship, /council-ship, "council ship", "review and ship this", "council review and merge", "run the council then ship it", or anything matching "council + ship/merge/deploy", redirect to /ro:council-review with --fix --ship.
npx skillsauth add RonanCodes/ronan-skills council-shipInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This is a thin alias for /ro:council-review --fix --ship. Both invocations resolve to the same behaviour.
Use /ro:council-review directly for the full skill body and every flag. /ro:council-ship exists so the whole review-fix-merge-deploy loop is one word.
What the one gesture does: run the council review, dispatch implementer agents on the findings, re-review until the verdict clears (max 3 rounds), then hand the branch to the /ro:ship flow (local gate, push, PR, squash-merge per the ro ci policy, deploy). Typing this alias IS the explicit merge authorization the council's never-auto-merge rule requires. If the verdict does not clear, the run stops without merging and prints the standard Pickup command.
See skills/council-review/SKILL.md for:
--fix loop, implementer routing, and the Council-review: commit trailer--ship semantics (section 6b) and the stop-without-merge rule--post/ro:council-ship # same as /ro:council-review --fix --ship
/ro:council-ship 142 # same as /ro:council-review 142 --fix --ship
/ro:council-ship --block-on critical+major # stricter gate before shipping
All flags supported by /ro:council-review are supported here.
testing
--- name: linear-pipeline description: The Fable orchestrator for a single dispatched Linear ticket. Holds almost no context itself; it receives `--issue <ID> --detached`, decides the stage sequence, and fans out a sub-agent per stage, passing forward only each stage's artifact (never re-derived, never inlined into its own context). Step zero, before any planning or stage routing, is a boundary triage against `canon/security-boundary.md` (#199): a match tags Ronan Connolly and stops the run, no
development
--- name: in-your-face description: Capture a chat-only answer into a durable artifact (markdown + HTML, PDF when cheap) and launch it automatically so the user cannot miss it. Use when user says "in your face", "don't let me lose this", "save that answer", "make that durable", or right after answering a substantive side question (a recipe, comparison, how-to, or generated prompt) that would otherwise die with the context. category: workflow argument-hint: [--no-open] [--vault <short>] [hint of
tools
One-shot headless OpenAI Codex CLI calls for background/admin AI tasks — summaries, classification, extraction, admin glue. The default engine for anything that runs AI constantly in the background (daemon-driven, per-event), because it bills the flat ChatGPT subscription instead of Claude usage or per-token API spend, and it keeps working while Claude is rate-limited. NEVER for coding — coding stays Claude. Use when a skill or daemon needs a cheap always-on AI call, when the user says "use codex", "ask codex", "codex as backup", or when building a background summarizer/classifier into a listener or loop. Reads auth from ~/.codex/auth.json (ChatGPT account, no API key).
research
Turn a warranty rejection, repair quote, or RMA email into a cited decision brief — legal read (NL/EU consumer law), is the part user-serviceable, live part and new-unit prices, repair-vs-DIY-vs-new economics, before-you-send-it checklist, deadlines. Use when the user pastes or screenshots a repair quote, warranty rejection, "not covered" email, onderzoekskosten fee, or asks "should I repair or replace this".