coalesce-labs/catalyst

Token-efficient Claude Code workspace with parallel agents and persistent memory. Research → Plan → Implement → Validate workflow.

20Stars on the repository
60Mods indexed here, across every type
4d agoLast push, which is what freshness is scored on
noneNo LICENSE: all rights reserved, so bodies are not copied

setup-catalyst

01

coalesce-labs/catalyst

Skill Claude CodeCodex

Diagnose and fix Catalyst setup issues. Validates tools, database, config, OTel, direnv, the Catalyst Cloud replica mirror, and thoughts. Automatically fixes what it can — creates directories, initializes the database, sets WAL mode, runs migrations. Use for new installs, upgrades, or when something isn't working.

20 4d ago C 69 tokens

coalesce-labs/catalyst

Skill Claude CodeCodex

Validates YAML frontmatter on plugins//skills//SKILL.md and plugins//agents/.md against docs/frontmatter-standard.md and .claude/rules/plugin-editing.md: required fields, the disable-model-invocation/user-invocable polarity, allowed-tools vs tools, and skill-only fields that must not leak (model, category). Use when…

20 4d ago A 112 tokens

agent-browser

03

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Fast browser automation CLI for AI agents. ALWAYS use instead of Playwright MCP tools for web testing, screenshots, form filling, and UI verification. Use when user says "open in browser", "check the site", "take a screenshot", "fill the form", "test the UI", or any browser interaction. Also use as a fallback when a…

20 4d ago A 101 tokens

ask

04

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Ask/decision tickets ("what needs me") — the Catalyst-wide SOP for raising a human decision as a Linear ticket, replying in-thread as the app actor, and closing it when the answer lands. Use whenever an agent needs a human to decide or click something, or for any ticket labelled catalyst-ask / ask/decision.

20 4d ago A 73 tokens

briefing-followup

05

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Interactive walk-through of today's morning briefing. Loads the briefing markdown at thoughts/briefings/YYYY-MM-DD.md (built by morning-briefing), parses its decisions block, and walks the user through each open decision — approve / reject / defer, schedule a calendar entry, file a Linear ticket, launch a relay-ticket…

20 4d ago A 137 tokens

commit

06

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save their work, commit changes, or says 'commit this', 'save my changes', 'let's commit'. Auto-detects commit type, scope, and ticket reference from branch name.

20 4d ago A 60 tokens

compound-estimate

07

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Closing ritual for the AI-native estimation feedback loop. 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 relay-native trigger this skill now shares with ticket-retro and ticket-compound, see references/trigger.md…

20 4d ago A 186 tokens

concierge

08

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

The ONE agent a human talks to. Use when a human comments on their Concierge — ticket, on the status board, or on any scope no steward owns; when a new project must be scaffolded from a request; or when an ask has gone unanswered. Owns the board, the ask inbox, and routing. Never commands a steward.

20 4d ago A 77 tokens

create-handoff

09

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Create handoff document for passing work to another session. ALWAYS use when the user says 'create a handoff', 'hand this off', 'save progress for later', 'I need to stop here', or when context usage is high (>60%) during implementation and work needs to continue in a fresh session.

20 4d ago A 69 tokens

create-plan

10

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

Create detailed implementation plans through an interactive process. ALWAYS use when the user says 'plan this', 'create a plan', 'let's plan the implementation', 'design the approach', or wants a structured TDD implementation plan before writing code. Works best after /research-codebase.

20 4d ago A 62 tokens

create-pr

11

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 71 tokens

create-worktree

12

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago B 57 tokens

describe-pr

13

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 54 tokens

fix-typescript

14

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 70 tokens

gherkin-ticket

15

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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 (…

20 4d ago A 118 tokens

implement-plan

16

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 64 tokens

iterate-plan

17

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 64 tokens

linear

18

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 61 tokens

linearis-cli

19

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 71 tokens

merge-pr

20

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.

20 4d ago A 67 tokens

morning-briefing

21

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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…

20 4d ago A 131 tokens

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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…

20 4d ago A 77 tokens

remediate-plan

23

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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.…

20 4d ago A 160 tokens

research-codebase

24

coalesce-labs/catalyst

Skill Claude CodeCodex

Part of catalyst-dev

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…

20 4d ago A 78 tokens

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: