agentleFS
Sign inStart free
ysamlanysamlan/agent-log-gif/.claude/skills/worktree-setup/SKILL.md

worktree-setup

Skill9 starsChanged 8 months agoApache-2.0View on GitHub

Set up a git worktree for isolated development on agent-log-gif. Use this skill whenever you're working in a fresh worktree or isolated environment — covers venv creation, dependency sync, and verification. Trigger when entering a worktree, when setup fails in a worktree, or when the user mentions worktree setup.

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. robinebers/skills★ 48same name
    2. niieani/caara★ 4same name
    3. TeamSPWK/nova★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When working in a git worktree or fresh environment for agent-log-gif, follow these steps.

    line 10
  2. Very specific:

    If pre-commit hooks fail in a worktree with "venv not found" errors, it's because the hook is looking for the venv at the worktree root.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Worktree / Fresh Environment Setup

When working in a git worktree or fresh environment for agent-log-gif, follow these steps. The key requirement is that each worktree gets its own virtualenv — never share the main repo's venv.

Quick Setup

# 1. Create an isolated venv pinned to this worktree
export UV_PROJECT_ENVIRONMENT=".venv_devcontainer"
uv venv "$UV_PROJECT_ENVIRONMENT"
uv sync

# 2. Verify everything works
uv run pytest tests/ -q --tb=short

Why a Separate Venv?

Each worktree must have its own venv. If worktrees share a venv with the main repo, editable installs (pip install -e .) will point at whichever source tree was installed last, causing confusing import mismatches. Set UV_PROJECT_ENVIRONMENT so all uv commands in that shell use the worktree-local venv:

export UV_PROJECT_ENVIRONMENT=".venv_devcontainer"

The .venv_devcontainer/ directory is already gitignored project-wide.

Pre-commit Hooks

If pre-commit hooks fail in a worktree with "venv not found" errors, it's because the hook is looking for the venv at the worktree root. Fix: run uv venv .venv_devcontainer && uv sync in the worktree.

Running the Tool in a Worktree

Same commands as the main repo — just and uv run work as normal once the venv is set up:

just test                    # run tests
just lint                    # lint and format
uv run agent-log-gif json tests/sample_session.jsonl -o /tmp/test.gif

Worktree Working Directories

Claude Code agent worktrees live under .claude/worktrees/ and are gitignored.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free