TomerAberbach

Resolve conflicts in the current `jj` commit.

Use when writing, reviewing, or modifying property-based tests, such as those using `fast-check`, or when asked to add test coverage.

Check a design decision against how comparable real tools solved it, citing a verifiable source for every claim.

Replace jargon and imported metaphors in code and prose with concrete, domain-fitting terms a reader understands without translation.

Make a set of things (code, prose, config, docs) consistent along a dimension the user names, by picking a canonical form and conforming every member to it.

Diagnose a failing, cancelled, or hanging CI run, explaining why it fails in CI when the same command passes locally.

Find interface boundaries that leak their implementation and close the leaks, so each module hides one coherent decision behind an interface stated in its callers' terms.

Write a description for the current `jj` commit.

Create a new Claude Code skill following the conventions of existing skills.

Do an editorial review of a post or article and report findings ordered by importance.

Attempt a task in a clean-room Claude Code session that has none of this session's context and none of the project's agent instructions, and report the friction log it kept.

Remove illegal states from data structures by redesigning their types so the illegal states cannot be represented at all.

Perform a task with a worker agent, critique it with an adversary agent, and apply the accepted critiques with a reconciler agent.

Remove unnecessary comments from code: tombstones, redundant restatements, and comments a well-named variable or function would replace.

Update implementation to satisfy added, updated, or deleted tests in the current commit.

Rename a concept everywhere: propose candidate names with tradeoffs, let the user pick, then sweep the winner through identifiers, prose, docs, and skills.

Use when writing, reviewing, or modifying any test files, or when asked to add test coverage.

Add, update, or delete tests for changes in the current commit.

Generate a performance profile, identify hotspots, and optimize.

Update a project's SKILL.md files to match the code they describe.

Distill a project's transcripts into proposals for eliminating repetitive work: skills, scripts, hooks, rules, or fixes to whatever causes the repetition.

Update the project's CLAUDE.md to match its current structure and conventions.

Extract a DDD-style ubiquitous language glossary.md file from the current conversation and codebase, flagging ambiguities and proposing canonical terms.

Settle an unnamed unease about a piece of code by naming the design defect behind it or ruling the unease unfounded, then handing off to the skill that fixes it.

Audit something against a standard, check every item in scope, and report the findings and the coverage behind them.

Write, fill in, or update a GitHub issue, including an upstream bug report with a minimal reproduction, and judge replies to it.

Find opportunities for code reuse in the changed code, both against existing code and within the change itself, without creating bad coupling or contrived abstractions.

Produce a reading order for a codebase: a map of how data flows through it, a breadth-first pass over structure and interfaces, then optional depth-first dives per module.

Distill a body of data into a small artifact that keeps what matters: a research document, code that handles the data, a skill, a schema.

Split the current `jj` commit into multiple focused, self-contained, easy to review commits.

Move code that ended up in the wrong place to where it belongs: the right file, module, layer, or package.

Refactor code so each function, class, and module sits at a single level of abstraction and reads top-down as a narrative.

Split the current `git` commit into multiple focused, self-contained, easy to review commits.