proomt

Search

Search posts, papers, and topics

All posts

Bjørn Johansen4 min readintermediate

One command per issue: git worktree, tmux and Claude Code

Read on bjornjohansen.com

Summary

The post introduces `claude-work`, a Bash helper that creates a git worktree, starts a tmux session, and launches Claude Code for a given issue, keeping each AI‑driven task isolated. It also handles safe re‑attachment and cautious cleanup to avoid losing work.

  • Use git worktree to create per‑issue isolated checkouts, avoiding branch clutter in the main repo.
  • Wrap worktree creation, tmux session start, and Claude Code launch in a single script (claude-work) for repeatable workflow.
  • The script safely re‑attaches to existing worktrees/sessions and only deletes them after confirming no uncommitted changes.
  • Installation via a self‑contained Bash installer that verifies SHA256 and respects user permissions.

Engineers using AI coding assistants need isolated environments to prevent cross‑issue interference and safe cleanup.

6/10
devopscliautomationgittmux

Related reading

  1. Blog: How to Build a DevOps Agent

    This blog walks through the open‑source DevOps Agent Kit, which lets Claude Code or Cursor act as a DevOps assistant by connecting to CloudBees Unify, Jira, and Slack via MCP servers and to GitHub via the CLI. It provides a repeatable setup (Docker, Node, env file) and seven slash commands for pipeline overview, triage, security, release readiness, flag management, CI health scoring, and Jira tic…

    Codeshipcloudbees.com10 min

  2. Reinventing issue tracking: Local-first and Git-native

    A devlog describing how Manganin’s issue tracker stores issues in a dedicated Git repo as plain files, after rejecting earlier approaches that tried to embed issue data in the code tree or Git refs. The author explains the pitfalls of using refs for issue storage, shows the low‑level Git commands needed for that approach, and then outlines the final design: a hidden sister repository where each i…

    Lobstersmanganin.dev6 minHN1lobste.rs27

  5. One style guide for everything Claude Code writes

    A detailed walkthrough of forking the nbj‑write‑clearly Claude Code skill to enforce the Google Developer Documentation style guide across all developer‑facing prose (docs, comments, commit messages, review feedback). The fork expands the trigger set, vendors the 70‑page guide offline via a Bun sync script, and adds a layered approach (global CLAUDE.md rules, on‑demand skill, per‑agent preloaded…

    Bjørn Johansenbjornjohansen.com5 min

  6. Agora: Git as Shared Memory for Collective AutoResearch

    Agora treats a Git repository as a shared, append‑only memory for autonomous research agents, recording each claim as an immutable commit in a DAG. In a 12‑day run with 13 language‑model workers it generated 1,703 reproducible contributions and closed 62 % of the gap to a trained GPT‑2‑124M, demonstrating that shared research state can accelerate discovery.

    Hugging Face Daily Papersarxiv.org2 minpaper