scottsauberlt

name	concise-pr
description	Concise PR title/description format. Use whenever creating a pull request, writing or editing a PR description, or when asked to clean up a verbose PR body.

Concise PR format

Every PR description is exactly two sections:

scottsauberlt

Error in user YAML: (<unknown>): mapping values are not allowed in this context at line 2 column 66

---
name: ship-it
description: Carries one work item from idea to a review-ready PR: grill the plan → implement → verify → code review → security review → see it run → draft PR → green CI → PR comments → hand off. Use when the user wants the whole thing carried through or says "ship it".
---

Ship It

Carry one work item from idea to a review-ready pull request, autonomously, in this codebase. After the human approves the plan, you run the whole pipeline hands-off, stopping only at a small set of human gates. The goal is that the human grills the

scottsauberlt

#!/bin/bash
# Claude Code status line: context token usage + usage limits + git working-tree summary.
# Receives session JSON on stdin (see code.claude.com/docs/en/statusline).
input=$(cat)

# --- Context window usage (provided directly, no transcript parsing needed) ---
tokens=$(printf '%s' "$input" | jq -r '.context_window.total_input_tokens // 0')
pct=$(printf '%s' "$input" | jq -r '(.context_window.used_percentage // 0) | floor')
exceeds=$(printf '%s' "$input" | jq -r '.exceeds_200k_tokens // false')

scottsauberlt

name	grill-story
description	Interview the Product Owner relentlessly about a backlog item until it would survive Refinement — surfacing every question the delivery team will ask before they ask it. Use when a PO wants to stress-test a user story, prep a backlog item for refinement/grooming, check it against the Definition of Ready, or mentions "grill my story".

Interview me relentlessly about this backlog item until we reach a shared understanding that would survive Refinement. Your job is to be the whole delivery team at once — the skeptical senior dev, the QA who lives in the edge cases, the designer, the person who has to support this in production — and ask every question they will ask, before they ask it.

Walk down each branch of the story one-by-one, resolving dependencies between decisions as you go. For each question, provide your recommended answer so I'm reacting to a concrete proposal, not staring at a blank page.

scottsauberlt

#!/bin/bash
# Claude Code status line: context token usage + usage limits + git working-tree summary.
# Receives session JSON on stdin (see code.claude.com/docs/en/statusline).
input=$(cat)

# --- Context window usage (provided directly, no transcript parsing needed) ---
tokens=$(printf '%s' "$input" | jq -r '.context_window.total_input_tokens // 0')
pct=$(printf '%s' "$input" | jq -r '(.context_window.used_percentage // 0) | floor')
exceeds=$(printf '%s' "$input" | jq -r '.exceeds_200k_tokens // false')