Skill Claude CodeCodex
Use when backporting the commits between two release tags onto a hotfix branch in / : find the patch milestone and duplicate those commits onto the tag with jj.
Skill Claude CodeCodex
Use when probing uncertain results in a disposable sandbox — large investigation, development, debugging, testing, UAT, white-room, or data validation before promoting a change.
Skill Claude CodeCodex
Use when splitting multi-unit work into parallel, isolated jj workspaces (depth-tree fan-out) and landing as independent plain gh pr merges.
Skill Claude CodeCodex
Use when committing in a target-org repo: plain-English imperative titles and repo-enforced hooks (gitlint, DCO) win.
Skill Claude CodeCodex
Use when jj conflicts or divergent changes block a jj repo after a tree move — resolve conflicted revisions and divergent twins until pushable.
Skill Claude CodeCodex
Use when updating, improving, compressing, or token-optimizing a skill or profile in a skills catalog: rework the body, tighten it, refresh evals, and keep it loadable.
Skill Claude CodeCodex
Use when triaging an existing org discussion: category, body shape, Q&A answer, and conversion to an issue.
Skill Claude CodeCodex
Use when opening an RFC Discussion in the target org as the pre-issue stage: converge on the problem, then derive the issue.
Skill Claude CodeCodex
Use when documenting a project in the repo's docs/ directory after a behavior-changing PR.
Skill Claude CodeCodex
Use when reclaiming resources leaked by jj-based agent workflows — dangling bookmarks, skill-created jj workspaces, and leftover working-copy dirs from sks-async/sks-dev.
Skill Claude CodeCodex
Use when investigating a bug, test failure, build break, or unexpected behavior — find root cause, form a hypothesis, and propose a solution, never apply the fix itself.
Skill Claude CodeCodex
Use when iterating a problem to convergence inside its GitHub issue via research and comments before deriving the PR.
Skill Claude CodeCodex
Use when triaging an existing org issue: assign type, labels, assignee, milestone, project, relationships, and fields; close with rationale if not workable.
Skill Claude CodeCodex
Use when opening an issue in an org repo: body is the problem statement, acceptance criteria as a command-decidable tasklist; owns the create → triage order.
Skill Claude CodeCodex
Use when landing a target-org PR after reconciliation (sks-pr-resolve) and review approval gates pass; closes the linked issue deliberately.
Skill Claude CodeCodex
Use when resolving a PR's review conversations, including CodeRabbit review comments, checking the DoD ledger, and reconciling before merge (no merge itself).
Skill Claude CodeCodex
Use when reviewing code in an org repo: cross-check related issues, enforce YAGNI, root-cause fixes, and project conventions before approval.
Skill Claude CodeCodex
Use when triaging an existing org PR: labels, assignee, milestone, and reviewers.
Skill Claude CodeCodex
Use when opening a PR in a target-org repo: push to origin, --head org:branch, plain-English title, issue linkage, parity with commit, pre-submit isolation gate, opens as a draft.
Skill Claude CodeCodex
Use when rebasing a jj stack onto moved main leaves conflicts — restack, then resolve each conflicted revision with edit/resolve until pushable.
Skill Claude CodeCodex
Use when distributing a task across a cluster of agents over A2A — route by capability need, machine resource, and runner pressure, optionally in a disposable sks-adversarial sandbox.
Skill Claude CodeCodex
Use when isolating one unit of work in a fresh jj workspace — the mandatory entry to implementation for every unit, so concurrent WIP never folds in and bookmarks/pushes stay scoped.
Skill Claude CodeCodex
Use when reviewing an upstream NixOS/nixpkgs pull request: build the changed packages with nixpkgs-review and check the diff against nixpkgs conventions.
Skill Claude CodeCodex
Use when creating a brand-new skill or profile for a skills catalog: grounded body, evals, manifests, and ship through the dev workflow.
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: