jeremyronking

name

learn

description

Guided codebase exploration for understanding how something works or what a ticket will require. Accepts a Jira ticket ID, a free-form prompt, or both. Presents findings in digestible chunks with file references, prompting the user to proceed at each step. Designed for developers getting up to speed on an unfamiliar area. **RECOMMENDATION** use this skill within IDE context, so the user can easily navigate to referenced files and lines.

The user wants to explore and understand a part of the codebase — not implement anything yet. Input may be:

• A Jira ticket ID (e.g. MVSLLR-123)
• A free-form question or topic (e.g. "how does the proposal flow work?")
• Both together

jeremyronking

Install the unslop setup into Claude Code

This gist sets up the unslop skill and the two prose rules from the owner's global CLAUDE.md. The user who gave you this gist URL wants this machine to match theirs. Work through the steps in order and stop to ask whenever a step touches a file they may already have.

Files in this gist

Gists store files flat, so each file maps to a path under ~/.claude/:

Gist file	Install to

jeremyronking

name	spec-writer
description	Interactive specification writer that captures requirements and creates focused, phased implementation plans with requirements as GitHub issues or local spec files
argument-hint	feature or bug description

Purpose

Generate focused, precise implementation specs through an interactive Q&A process, breaking features into logical phases and creating specs in dependency order.

Audience: the specs are consumed by LLM implementing agents (of varying models and capabilities), not humans. Different models fill spec gaps differently — wherever a spec is ambiguous, each implementer invents a different answer. Precision converges them; narrative prose does not. Every rule below serves that goal: exact contracts, machine-checkable done-ness, explicit anti-goals, and zero undefined qualifiers.

jeremyronking

name	compose-work
description	End-to-end workflow that spec-writes a feature (using /spec-writer and /grill-me), creates GitHub issues, and queues Composer agent tasks. Accepts a description or existing GitHub issue URL.
argument-hint	description or GitHub issue URL

Purpose

End-to-end workflow that takes a feature idea from specification to a queued Composer agent task. Combines spec-writing (with /grill-me for clarity), GitHub issue creation, and Composer MCP task creation into a single orchestrated flow.

Key principle: Front-load ALL user interaction, then execute autonomously. Gather every decision (requirements, task type, model, effort) before creating issues or tasks. Once the user gives final approval, the entire creation pipeline runs hands-off.

jeremyronking

#!/bin/zsh
#
# daily-update.sh — keep Homebrew packages and global npm packages up to date.
#
# ─── What this script does ─────────────────────────────────────────────────
#   1. brew update   — refresh Homebrew's package metadata
#   2. brew upgrade  — upgrade installed formulae/casks
#   3. brew cleanup  — remove old versions and caches
#   4. npm update -g — update global npm packages within their semver ranges
#                      (does NOT bump major versions; that requires

jeremyronking

#!/bin/bash
# ==============================================================================
# Claude Code Status Line
# ==============================================================================
# This script creates a rich status line for Claude Code showing:
# - Current model being used
# - Mode (if in plan/edit mode)
# - Context window usage percentage
# - Token usage (input/output totals for the session)
# - Session cost in USD