Skip to content
TrustedSkillsbeta
Back to all skills

Flow Next Worktree Kit

Checked
gmickel·vlatest·backend·MIT

Automates Git workflow transitions between worktrees, streamlining development across multiple project branches.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add gmickel/flow-next --skill flow-next-worktree-kit -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

gmickel

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned gmickel/gmickel-claude-marketplace at d61e3536f9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 284 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The flow-next-worktree-kit skill provides tools for managing and interacting with Git worktrees. It enables the creation, switching, and listing of worktrees from within an AI agent's workflow. This allows agents to efficiently manage multiple branches or repositories without constantly checking out and back into main projects.

When to use it

  • Branch Isolation: When an agent needs to experiment with a feature branch or bug fix in isolation from the primary codebase.
  • Parallel Development: For tasks requiring simultaneous work on different parts of a project, such as integrating external libraries or developing plugins.
  • Repository Exploration: When an agent needs to quickly explore and test code within multiple repositories without impacting the main working directory.

Key capabilities

  • Create new Git worktrees.
  • Switch between existing worktrees.
  • List available worktrees.

Example prompts

  • "Create a worktree named 'experiment' from branch 'feature-x'."
  • "Switch to the worktree called 'bugfix-123'."
  • "List all my current Git worktrees."

Tips & gotchas

This skill requires a working Git environment and assumes familiarity with basic Git concepts. Ensure your AI agent has appropriate permissions to access and modify the Git repository.