Nathan myobie

name	review
description	Run consistent, findings-first code reviews with Codex CLI for any target: uncommitted/dirty working tree, current branch vs base branch, specific commit SHA, or pull request. Use when asked to review bugs, risks, regressions, and test gaps with actionable file/line findings.

Codex Review

Execute one-shot code review flows with Codex CLI and return review-quality findings.

1) Select review mode

ccmailbox pattern

Just files + a real Claude Code session. A folder with simple conventions that gives any local process fully async conversational, bidirectional communication with a running Claude Code session. No special hooks, no SDK, no patches. The Claude Code session continues to work, is not blocked, you can still work there too.

How it works

Agree on the folder location. The local process (web server?) sees all files Claude Code wrote into the folder.
The local process writes a file to requests/ (the mailbox folder) (web server can expose a POST so any browser can make new requests at any time)
CronCreate inside Claude Code polls the mailbox folder every minute
Claude reads the request, does work, and writes/edits files on disk into the folder

name

literate-review

description

Use when the user wants to review code changes interactively. Uses literate markdown documents served in a local web app. Works with one repo or many. Triggers on: 'review PR', 'review branch', 'review changes', 'literate review', 'set up a review', 'create review docs', 'review these branches'. Generates topic-organized markdown files with inline diffs and surrounding context, serves them with syntax highlighting and inline commenting, and watches for reviewer comments that the current Claude Code session can respond to.

Literate PR Review

Generate a topic-organized code review experience for changes in one or more git repositories. The output is a set of .diff and literate markdown files served in a local web app where reviewers can leave inline comments that Claude watches and responds to. Works equally well for a single branch in one repo or coordinated changes across many repos.

	export function saveURLToDisk(url: URL \| string, name: string) {
	const anchor = document.createElement('a')
	anchor.href = url.toString()
	anchor.download = name
	anchor.click()

	requestAnimationFrame(() => {
	anchor.remove()
	})
	}

	export function reactiveTextNode(signal) {
	const node = document.createTextNode(signal.value)

	effect(() => {
	node.textContent = signal.value
	})

	return node
	}

	#!/bin/bash

	mkdir -p alac

	for flac_file in ./*.flac; do
	base_name=$(basename "$flac_file" .flac)
	alac_file="./alac/$base_name.m4a"
	echo ffmpeg -i "$flac_file" -map 0:a -c:a alac "$alac_file"
	ffmpeg -i "$flac_file" -map 0:a -c:a alac "$alac_file"
	done

	#!/bin/bash

	# Usage: eval "$(bin/dot-env)"

	set -eo pipefail

	PROJECT=$(git rev-parse --show-toplevel)

	for f in ${PROJECT}/.env.*; do
	echo "# ${f}"

	import { mdx } from './mdx.ts'
	import renderToString from 'preact-render-to-string'
	import { type FunctionalComponent } from 'preact'

	const MDXContent = await mdx(new URL('./test.mdx', import.meta.url))

	const Page: FunctionalComponent = ({ children }) => (
	<html lang='en'>
	<head>
	<title>Example MDX page</title>