andynu

skill-postmortem

A Claude Code skill. Turns one observed skill failure into three artifacts with different lifetimes: a memory pattern that persists, a skill edit that may be reverted tomorrow, and a ledger entry recording which of those happened. The pattern is written before the edit is proposed, so reverting an edit never destroys the evidence that motivated it.

Adapted from WikiSkill: Compiling Agent Experience into Persistent Knowledge for Skill Evolution, Tang, Rashtchian, Ferng, Tomkins, Juan, Vu, 27 Aug 2026.

andynu

herdr-project — a prefix+f fzf project picker for herdr

herdr is a terminal workspace manager for AI coding agents (0.8.0 at time of writing). It has spaces, tabs, and panes, but no session-per-project layer the way tmux does, so "switch to project X" isn't a built-in. This is that binding.

Hit ctrl+a f, get an fzf popup listing every directory under ~/work/src and ~/projects, pick one, and land in a herdr space labelled with the project's basename whose first tab starts in that directory. If a space with that label is already open, it focuses that one instead of creating a second.

andynu

Conversation opened. 1 read message.

Skip to content Using Whitehead Institute for Biomedical Research Mail with screen readers 2 of 29,710 An idea for testing a multi-persona agentic review. Andy Nutter-Upham andy@wi.mit.edu

AttachmentsFri, Mar 13, 3:30 PM (17 hours ago)

andynu

allowed-tools	Glob(path:/home/andy/.claude/**), Read(path:/home/andy/.claude/**), Edit

Deduplicate Local CLAUDE.md

Remove content from the local project CLAUDE.md that duplicates global rules.

Instructions

andynu

tmx-claude & tmx-worktree

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.

Notes

• 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.

What's included

andynu

# 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   ║
# ║                                                                     ║

andynu

# 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

andynu

Two-Context Execution Pattern with Beads

A workflow pattern for AI-assisted development that separates planning from execution, using context isolation to keep each layer focused.

The Problem

Large tasks overwhelm a single Claude session:

• Context fills with implementation details
• Hard to track overall progress
• Easy to lose sight of the plan while deep in code

andynu

Multi-Agent Claude Code Workflow

A lightweight pattern for spawning secondary Claude Code sessions using tmux, enabling parallel work across projects without context collision.

Why Spawn Secondary Sessions?

When working from a "mission control" directory (like ~/work/src/ with 100+ projects), you often need to:

• Dispatch deep work to a specific project while continuing meta-level coordination
• Run parallel investigations that would pollute a single session's context

andynu

name	C4 Diagrams
description	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.

C4 Architecture Diagrams with D2

Create C4 model diagrams using D2's text-to-diagram syntax. Supports both graphical (SVG/PNG) and ASCII output.

---