Use when installing Zig, switching Zig versions, setting up ZLS, or resolving a Zig version mismatch - covers zvm (Zig Version Manager) for installing, pinning, and running specific Zig toolchains in a repository.
View the regent activity log for the default or selected session. The default view shows the conversation timeline and tool calls; file summaries are available with file flags.
Rewind workspace and conversation to a previous regent step. Non-destructive with automatic backup. Use when recovering from mistakes or exploring alternative paths.
Grace repository workflow, architecture, and implementation guidance. Use when working in a Grace repo or on Grace planning, GitHub issue orchestration, F#/.NET code, Orleans actors, Giraffe HTTP APIs, SDK or CLI surfaces, DTOs/events/parameters, authorization, webhooks and approval requests, manifest-backed storage…
Interacts with a running lightjj instance (browser-based Jujutsu/jj viewer) via the lightjj api CLI. Reads diffs, posts inline review comments, posts doc-mode suggestions, and steers the user's view. Use when the user has lightjj running and wants the agent to review changes, annotate diffs, or comment on markdown…
Add a single new stage to an existing Calkit pipeline. Use when the user invokes /calkit:add-pipeline-stage or asks to add a script, notebook, or command to the pipeline.
Calkit conventions and foundational context. Load whenever working in a Calkit project—defines calkit.yaml structure, environments, pipeline stages, CLI commands, and version control conventions.
Convert an existing repo with ad hoc scripts into a fully reproducible Calkit pipeline. Use when the user invokes /calkit:create-pipeline or asks to make a project reproducible end-to-end.
Operate Sophia CLI as an intent-first abstraction over Git for local repositories. Use when the user wants to initialize Sophia, open/manage Change Requests (CRs), define CR and task contracts, checkpoint task progress with explicit scope, inspect impact/validation/review/status context, repair metadata, and merge…
Commit changes as Drift intents (semantic versioning layer on git) and trace why code exists. Use when the repository has a .drift/ directory and the drift CLI (or the @drift/mcp MCP server) is available.
Universal Dolt version-control workflow. Step 0 auto-detects what kind of Dolt stack is present — every make and model (classic Dolt repo, live dolt sql-server on its ACTUAL bound port, bd embedded store, Doltgres, DoltLite single-file DB, DumboDB) — and emits a ready-to-use connection descriptor, then routes to work…
Use this skill for repositories managed through the git-mcp server when the task involves Git inspection, staging or committing, branches, remotes, rebase, cherry-pick, stash, bisect, worktrees, Git Flow, LFS, release tagging, PR preparation, or recovery. Prefer git-mcp tools over shell git commands, including when…
Use this skill when a repository may be managed by GitButler. Detect GitButler availability with gitbutcheck, then prefer the but CLI or but mcp server for version control in GitButler-managed repositories. Run but teardown before using git-mcp tools on a GitButler-managed repo so plain-Git writes do not conflict with…
Use this skill when a repository may be managed by Jujutsu (jj). Detect jj availability and management with gitjjcheck, then prefer the jj CLI for all version control operations in jj-managed repositories. git-mcp tools operate on the underlying .git and will not reflect jj's change model (working-copy commit…