| allowed-tools |
|---|
Glob(path:/home/andy/.claude/**), Read(path:/home/andy/.claude/**), Edit |
Remove content from the local project CLAUDE.md that duplicates global rules.
Spawn Claude Code sessions in tmux windows — either in your current repo or in isolated git worktrees. Lets you run multiple Claude agents in parallel without blocking your terminal.
WORKTREE_BASE defaults to ~/work/src/ in tmx-worktree and worktree-clean. Edit the variable at the top of each script to match your layout.tmx-claude --help mentions bd-lite, a lightweight issue tracker I use. You can ignore that or rip it out.| # frozen_string_literal: true | |
| # ╔══════════════════════════════════════════════════════════════════════╗ | |
| # ║ WARNING: ruby-oci8 ONLY ║ | |
| # ║ ║ | |
| # ║ This patch uses cursor.rowid, a ruby-oci8 API. It is NOT ║ | |
| # ║ compatible with JDBC (JRuby). For a cross-platform fix that ║ | |
| # ║ handles composite primary keys only, see: ║ | |
| # ║ https://gist.github.com/andynu/508ed5b16f348d474db377ab1e870778 ║ | |
| # ║ ║ |
| # frozen_string_literal: true | |
| # Monkey patch: Fix LOB writes for tables with composite primary keys | |
| # | |
| # The stock oracle-enhanced adapter's write_lobs method assumes a single | |
| # primary key column. With a composite key, klass.primary_key returns an | |
| # Array, which causes: | |
| # - attributes[[:col_a, :col_b]] → nil (Hash doesn't find Array keys) | |
| # - quote_column_name([:col_a, :col_b]) → garbage column name | |
| # - SELECT FOR UPDATE returns no rows → RecordNotFound / data loss |
A workflow pattern for AI-assisted development that separates planning from execution, using context isolation to keep each layer focused.
Large tasks overwhelm a single Claude session:
A lightweight pattern for spawning secondary Claude Code sessions using tmux, enabling parallel work across projects without context collision.
When working from a "mission control" directory (like ~/work/src/ with 100+ projects), you often need to:
| name | description |
|---|---|
C4 Diagrams |
Creating C4 architecture diagrams using D2 diagram language. Use when creating system context diagrams, container diagrams, component diagrams, code diagrams, deployment diagrams, or any software architecture visualization following the C4 model. Also applies when discussing architecture at different zoom levels or explaining system boundaries. |
Create C4 model diagrams using D2's text-to-diagram syntax. Supports both graphical (SVG/PNG) and ASCII output.
| --- | |
| - name: ruby build dependencies | |
| apt: | |
| pkg: | |
| - git | |
| - build-essential | |
| - libssl-dev | |
| - zlib1g-dev | |
| - libreadline-dev | |
| - libffi-dev |
| #!/bin/bash | |
| input=$(cat) | |
| MODEL=$(echo "$input" | jq -r '.model.display_name // "Claude"') | |
| DIR=$(echo "$input" | jq -r '.workspace.current_dir // "~"') | |
| FOLDER="${DIR##*/}" | |
| # Git branch | |
| BRANCH="" | |
| if git -C "$DIR" rev-parse --git-dir > /dev/null 2>&1; then | |
| BRANCH=$(git -C "$DIR" branch --show-current 2>/dev/null) |
| description | argument-hint | allowed-tools | context |
|---|---|---|---|
execute a single bd issue |
<issue key> |
Bash(bd *), Bash(git *), Bash(tea *), Read(.) |
fork |
Execute a single bd issue with proper status tracking, commenting, and git workflow integration. This command handles one issue in isolation, keeping context clean.