Work In Slice

Community

paulinevos

work-in-slice

Do one owned slice in a Jujutsu workspace: make granular described revisions, keep its bookmark at the tip, fold fixes into their revision, rebase safely, navigate workspaces with jj-navi when it is installed, and hand off without publishing.

Overview

Publisher	paulinevos
Repository	`claude-stuff`
Skill name	`work-in-slice`
Stars	64
Forks	0
Bundled files	1
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by paulinevos on GitHub. Read the source before you install it.

Installation

Install the Work In Slice AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/paulinevos/claude-stuff/tree/main/plugins/jj-workflow/skills/work-in-slice
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/paulinevos/claude-stuff/tree/main/plugins/jj-workflow/skills/work-in-slice

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/paulinevos/claude-stuff.git /tmp/claude-stuff
mkdir -p .claude/skills
cp -r /tmp/claude-stuff/plugins/jj-workflow/skills/work-in-slice .claude/skills/work-in-slice

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Work In Slice in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Work In Slice on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Work In Slice is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

work-in-slice

Own only the assigned workspace, bookmark, and descendant change IDs. Work there, never in another worker's directory.

Confirm @ is an empty change on the assigned base:

sh
jj workspace root
jj log -r '@ | @-' --no-graph -T 'change_id.short() ++ " " ++ if(empty, "(empty) ") ++ description.first_line() ++ "\n"'

If it is not, stop and tell the orchestrator.

Make one logical, independently passing revision at a time:
```
sh
jj status
jj describe -m 'Add retry policy to HttpClient'
jj new
```
Use an imperative, capitalised subject without a period; a body explains why. Create the bookmark after the first revision with jj bookmark create <slice> -r @-, then move it after every revision with jj bookmark move <slice> --to @-.
Fold fixes rather than stacking follow-ups: jj squash --into <change-id>; use jj absorb for line-based ancestor fixes, jj split to separate work, jj describe -r to reword, and jj rebase -r ... -B ... to reorder. Refer to revisions by change ID, not commit ID.
When the base moves: jj git fetch && jj rebase -b <slice> -o <base>; resolve recorded conflicts in their revision (jj new, edit, jj squash), then return to the tip with jj new <slice>. A stale-workspace error means stop and use sync-workspace.
Before hand-off, leave @ empty, run jj status, ensure all slice revisions are described and conflict-free, and report the workspace, bookmark, and ordered revision list. Do not push or forget the workspace.

Never use --ignore-immutable. Snapshot with jj status before pausing; rewriting an active descendant's ancestor risks a divergent recovery.

If navi --version succeeds, jj-navi can handle workspace navigation; navi switch and navi doctor are safe for a worker, while navi list and navi merge belong to the orchestrator. Offer the install when it is missing rather than running it. None of the steps above change.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/jj-navi.md6 KB

Frequently asked questions

What does the Work In Slice AI skill do?

Why use Work In Slice on TypingMind?

Because you install it once and use it with any model. Work In Slice is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Work In Slice in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/paulinevos/claude-stuff/tree/main/plugins/jj-workflow/skills/work-in-slice. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Work In Slice?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Work In Slice?

As many as you like. As long as a model supports skills, you can use Work In Slice with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Work In Slice AI skill free?

Yes. It is published on GitHub by paulinevos under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Autoreview

openclaw

OrganizationPopular

Structured code review when explicitly requested, preferring OpenAI/Codex before Claude.

Claw Score

Audit or refresh OpenClaw maturity scorecard docs from root taxonomy, maturity scores, and QA evidence artifacts without using maintainer discrawl data or committed inventory reports.

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Control Ui E2e

Use when designing, testing, fixing, or extending the OpenClaw Control UI GUI, including UI stress-test galleries with feedback inputs, Vitest + Playwright end-to-end checks, mocked Gateway flows,…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

work-in-slice

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now