Create pull request with automatic Linear integration. ALWAYS use when the user says 'create a PR', 'open a pull request', 'ship this', 'ready for review', or wants to push changes and create a GitHub PR. Handles commit, rebase, push, PR creation, description generation, and Linear ticket update.
Create a git worktree for parallel work and optionally launch implementation session. ALWAYS use when the user says 'create a worktree', 'work in parallel', 'start a worktree for', or needs to work on multiple features simultaneously without switching branches.
Generate or update PR description with incremental changes. ALWAYS use when the user says 'describe the PR', 'update PR description', 'generate PR description', or after pushing new commits to an existing PR. Supports incremental updates that preserve manual edits.
Fix TypeScript errors with strict anti-reward-hacking rules. ALWAYS use when the user says 'fix type errors', 'fix typescript', 'type-check is failing', or when TypeScript compilation errors need to be resolved. Ensures runtime type safety — fixes root causes instead of silencing errors with casts.
Shape every ticket around a scannable use-case before it's filed. ALWAYS use when the user says 'file a ticket', 'create a ticket', 'file tickets for', 'open an issue', 'add a ticket', 'log a bug', or whenever drafting, titling, or rewriting a ticket. Turns vague, implementation-first tickets into an outcome title (…
Implement approved technical plans from thoughts/shared/plans/. ALWAYS use when the user says 'implement the plan', 'start implementing', 'build from the plan', or wants to execute a previously created implementation plan using TDD (Red-Green-Refactor). Supports team mode for parallel implementation.
Update existing implementation plans based on feedback or changed requirements. ALWAYS use when the user says 'update the plan', 'change the plan', 'the requirements changed', 'revise the approach', or wants to modify an existing plan in thoughts/shared/plans/ after review feedback or discovered issues.
Manage Linear tickets with workflow automation. ALWAYS use when the user says 'create a ticket', 'update the ticket', 'move ticket to', 'search Linear', or wants to create tickets from thoughts documents, update ticket status, or manage the Linear workflow. Uses Linearis CLI.
Linear access rule + Linearis CLI reference. READS → query the local replica by direct SQL (/catalyst/catalyst-replica.db); WRITES and list/search → the linearis CLI. Use when working with Linear tickets, cycles, projects, milestones, or ticket IDs like TEAM-123.
Safely merge PR with verification and Linear integration. ALWAYS use when the user says 'merge the PR', 'merge this', 'ship it', or wants to merge an approved pull request. Runs tests, checks CI, verifies approvals, squash merges, cleans up branches, and moves Linear ticket to Done.
Generate a daily briefing markdown at thoughts/briefings/YYYY-MM-DD.md with six sections — Review yesterday, Surface decisions, Plan today, relay-dispatch candidates, Friction since last briefing, and Learnings since last briefing — synthesized from Linear, GitHub, Granola, Google Drive, Google Calendar, and the…
Run the project orchestrator — the long-lived, single-threaded owner of ONE project that moves ready backlog tickets to Todo, lets the fleet scheduler dispatch them, watches the work, and communicates in threaded Linear comments. Use when asked to run/own/coordinate a project or its backlog. It never dispatches a…
Fixes what /catalyst-dev:validate-plan just found, in the same session. Consumes validate-plan's actual output — the Validation Report it renders into the conversation, since validate-plan has no Write tool and produces no verify.json — and applies the fixes directly via Edit/Write, re-runs a scoped gate, and commits.…
Conduct comprehensive codebase research using parallel sub-agents. ALWAYS use when the user asks to 'research', 'investigate', 'explore the codebase', 'how does X work', 'find out about', or needs deep analysis of how existing code is structured. Produces a research document in thoughts/shared/research/ with file:line…
Resume work from a handoff document. ALWAYS use when the user says 'resume handoff', 'pick up where we left off', 'continue from handoff', or provides a handoff document path. Verifies current codebase state against handoff, validates changes, and creates an action plan.
Systematically pull, categorize, and address all PR review comments — code change requests, questions, and suggestions. This skill fetches comments via gh api, groups them by file, implements fixes, handles disagreements diplomatically, and pushes a single commit. You should not try to handle PR review feedback…
Scan TypeScript code for reward hacking patterns — shortcuts that make linters pass without actually fixing type safety. This skill has a comprehensive checklist of 8 forbidden patterns with severity tuning (libraries vs apps) that you cannot reliably check on your own. ALWAYS consult this skill when the user says…
The long-running owner of ONE initiative or project. Use when asked to run, drive, coordinate or own a project, when a human comments inside a scope you hold, or when resuming from a handoff. Dispatches by launching /relay-ticket sessions, reading their reports, answering in threads, keeping status current.
Compound-engineering capture + curation for a finished ticket — the engineering feedback loop. Harvests the Friction sections that phase agents left in their artifacts plus the git diff, writes a structured entry to the shared learnings store (thoughts/shared/learnings/), prunes/amends stale notes there autonomously…
Cross-ticket retrospective VIEW (CTL-789 Loop C / CTL-814). ALWAYS use when a ticket's PR has merged and merge-pr's post-merge deploy-verification (CTL-2232) has resolved a terminal sentinel for it (the workflow's compound closing step — relay-native trigger, CTL-2244; see ../compound-estimate/references/trigger.md)…
Drive an aging pull-request backlog to zero. Inventories every open PR, finds the STRUCTURAL blockers first (a required check that can never run, a reviewer that never fires, chronically red CI), triages every unresolved review thread in parallel and VERIFIES each finding against the code before fixing it, then merges…
Validate that implementation plans were correctly executed. ALWAYS use when the user says 'validate the plan', 'check if the plan was implemented correctly', 'verify the implementation', or after completing /implement-plan to confirm all phases were properly executed and success criteria met.
Run the full 5-step TypeScript validation gate: type check, reward hacking scan, test inclusion, tests, and lint. This skill provides a structured multi-step pipeline that you cannot replicate on your own — it detects the project's package manager and linter automatically, checks tsconfig strictness, and invokes…
Setup, maintenance, and compounding upkeep of the Catalyst framework and the thoughts/ knowledge base: framework diagnostics/repair (setup-catalyst), terminal launcher config (setup-warp), and research-doc curation (research-curate). Future home for the compound-engineering retro/learning loop.