Explore skills
Showing 28111–28140 of 71536 skills
Bug-fix routine that fixes the whole class of bug, not just the reported instance. Use for any bug report, failing production behaviour, monitoring alert, audit finding or review finding that does real harm (a smaller review finding goes on the item's list, as ship-check says), and whenever the same kind of bug has been seen before. Reproduces it with a failing test, names the failure class, searches the task's scope for the same pattern (the whole codebase when the user's own prompt asks for the fix, not when it is picked from a task's list), fixes or records every hit, and adds the rule, invariant, helper or check that stops it coming back.
joetawil7/first-pass
Stars: 120Claude CodeCodexLearns the words a user habitually writes to their coding agent that make its answers worse ("be 100% sure", "don't assume", "full review", "are you sure?", "all fine, right?"), from what they actually typed in their recent Claude Code sessions. Shows what each one does, what went wrong after it, and what to say instead, then writes the habit words block that maps each word to the checks it should trigger, so the checks run without the words. Use when asked to learn, read, refresh or review the user's habit words or prompts, "which of my words make you worse", from setup-first-pass's profile step, or when the start-of-session check says the habit words are due.
joetawil7/first-pass
Stars: 120Claude CodeCodexSets up, checks or changes the optional Jev judge, the TypeSafe decision model that ship-check asks about review findings (is this real harm, is a small one worth fixing now, what proof does a small fix need). Shows whether it is on for each repo, which key it uses, switches it on or off, and sends one test request. Runs only when the user types it.
joetawil7/first-pass
Stars: 120Claude CodeCodexRun before writing or changing code for any feature, bug fix or refactor that touches data, jobs, money, outside services or user-facing behaviour. Finds where the change will break before it is built, by walking ten named failure classes (twice, halfway, outside call, failure-is-not-empty, neighbors, endings, money, hostile user, words, scale and time) against the code, and writes the answers into the plan. Use when planning a change, when asked to "think it through", "cover the gaps", "make sure it's bug free", or before any edit to payment, publishing, deletion, auth or background-job code.
joetawil7/first-pass
Stars: 120Claude CodeCodexReviews a change before it is merged, from little or no input. With nothing typed it reviews the branch you are on, uncommitted work included, against its base, its PR and its ticket, so a developer can check their own work before asking for review. With PR links, repo#N or a branch it reviews someone else's change the same way, several repos at once. It judges the failed CI checks and every Bugbot and reviewer comment, gets a fresh breaker review, traces every other piece of code that uses what changed, proves each finding or marks it unproven, says what the merge needs (a build, env vars, migrations, deploy order) and how to check the deploy, never posts to GitHub, and offers fixes only after the report. Runs only when the user types it.
joetawil7/first-pass
Stars: 120Claude CodeCodexRewrites the prompt typed after the command before any work starts, then works from the rewrite. Splits a mixed-up message into a numbered list of asks, turns words like "be 100% sure", "cover all cases" or "don't break anything" into the checks they stand for, keeps every name, path, number and quote exactly, and stops to ask only where it would have to guess. Runs only when the user types it.
joetawil7/first-pass
Stars: 120Claude CodeCodexThe definition of done. Run before calling any change done, fixed, verified, ready or shippable, for features and bug fixes alike. Checks the pre-mortem was answered, proves the tests fail on the old code, gets a fresh breaker review, runs CI's own checks in a clean checkout, checks the user-facing words, and writes the evidence report. Also use when asked "is it done", "is it ready", "did you verify it" or "can we merge".
joetawil7/first-pass
Stars: 120Claude CodeCodexCreate or inspect Convex accounts. Use when the user wants to set up a new account, check account details, or manage keys.
Convex-Dev/convex
Stars: 119Claude CodeCodexBuild the Convex project from source. Use when a contributor wants to compile, test, or package Convex.
Convex-Dev/convex
Stars: 119Claude CodeCodexIndex of the Convex Architecture Documents (CADs), the normative specifications for Convex. Use to find which CAD governs a subsystem before changing protocol, encoding, consensus or economic behaviour.
Convex-Dev/convex
Stars: 119Claude CodeCodexCAD3 encoding format — cells, embedded vs branch references, value IDs, validity rules. Use when working on encoders, decoders, serialisation, hashing or anything that reads or writes cell encodings.
Convex-Dev/convex
Stars: 119Claude CodeCodexResolve or register Convex Name System (CNS) names. Use when the user wants to look up a CNS name, register a new name, or update a name's target.
Convex-Dev/convex
Stars: 119Claude CodeCodexUse Convex DB — a lattice-backed SQL database. Use when helping users write queries, connect via JDBC or PostgreSQL clients, create tables, insert/query data, or use the direct lattice API.
Convex-Dev/convex
Stars: 119Claude CodeCodexConvex Lisp language reference — CVM conventions, calling library code, actor definitions, juice and error codes. Use when writing or debugging CVM source for queries, transactions or actors.
Convex-Dev/convex
Stars: 119Claude CodeCodexDeploy an actor (smart contract) to the Convex network. Use when the user wants to create a new on-chain actor with exported functions.
Convex-Dev/convex
Stars: 119Claude CodeCodexWork with DLFS, the Data Lattice File System — run a local DLFS server, manage drives, and read, write and list files through its MCP tools or WebDAV. Use when interacting with DLFS or working on the convex-dlfs module.
Convex-Dev/convex
Stars: 119Claude CodeCodexOrientation in the Convex ecosystem — what lives in which repository, where the specs and docs are, and which client libraries exist. Use when you need context that is not in this repository.
Convex-Dev/convex
Stars: 119Claude CodeCodexInspect and maintain an Etch store — Convex's content-addressed database. Use when examining peer storage, diagnosing corruption, garbage collecting, or reading data by hash.
Convex-Dev/convex
Stars: 119Claude CodeCodexTriage the open Convex issues against a fixed rubric — close what is done or superseded, give each a type label, and collect everything that needs a maintainer decision into one review sheet. Use when asked to review or triage all open issues.
Convex-Dev/convex
Stars: 119Claude CodeCodexJuice accounting — the cost of computation and bandwidth on the CVM. Use when reasoning about transaction execution cost, diagnosing a :JUICE failure, or pricing a new CVM operation.
Convex-Dev/convex
Stars: 119Claude CodeCodexRun isolated local Convex networks and in-process lattice node networks for development. Use when testing against local peers, reproducing peer or P2P replication issues, exercising NodeServer or P2PNode sync, or when no remote network is configured.
Convex-Dev/convex
Stars: 119Claude CodeCodexMemory accounting and allowances — the cost of on-chain storage, and how to minimise and reclaim it. Use when reasoning about state growth, diagnosing a :MEMORY failure, or designing actors that store data.
Convex-Dev/convex
Stars: 119Claude CodeCodexOperate a Convex peer — create, start, list, back up, or instantiate a network genesis. Use when running a peer against a network or setting up a new network.
Convex-Dev/convex
Stars: 119Claude CodeCodexProtocol versions, migrations and the v1 upgrade — which semantics to write against, and how to change CVM behaviour without forking the network. Use when changing core functions, juice costs, encodings or on-chain libraries.
Convex-Dev/convex
Stars: 119Claude CodeCodexExecute a read-only CVM query on the Convex network. Use when reading on-chain state, checking balances, looking up accounts, or evaluating Convex Lisp expressions.
Convex-Dev/convex
Stars: 119Claude CodeCodexCreate and manage fungible tokens on Convex. Use when the user wants to create a new token, check token balances, or manage token supply.
Convex-Dev/convex
Stars: 119Claude CodeCodexExecute a CVM transaction on the Convex network. Use when the user wants to modify on-chain state, call actor functions, or define values.
Convex-Dev/convex
Stars: 119Claude CodeCodexTransfer CVM coins or fungible tokens between Convex accounts. Use when the user wants to send coins or tokens to another account.
Convex-Dev/convex
Stars: 119Claude CodeCodexTrust monitors — Convex's composable on-chain authorisation model. Use when writing access control, restricting actor functions, defining who may mint or upgrade, or reviewing authorisation logic.
Convex-Dev/convex
Stars: 119Claude CodeCodexTransfer CVM coins or fungible tokens between Convex accounts. Use when the user wants to send coins or tokens to another account.
Convex-Dev/convex
Stars: 119Claude CodeCodex