joestump

Respond to review feedback on a PR — gather review comments, requested changes, and failing CI, make the code fixes on the PR branch, push, and reply to each thread explaining what was done. Use when the user says "respond to PR", "address review comments", "handle PR feedback", or "fix the review on PR

Build and query the SDD artifact graph. Use when the user wants to validate frontmatter edges, find impact/ancestors/chain for an ADR or spec, detect orphans or cycles, or backfill edges from prose. Currently supports validate / impact / ancestors / chain / orphans / cycles, with workspace-mode aggregation; backfill lands in Story 7.

Break an existing spec into trackable issues in your issue tracker. Use when the user says "plan a sprint", "create issues from spec", "break down the spec", or wants to turn requirements into tasks.

Review and merge PRs produced by /sdd:work using reviewer-responder agent pairs. Use when the user says "review PRs", "review the spec PRs", or wants automated spec-aware code review.

Pick up tracker issues and implement them in parallel using git worktrees. Use when the user says "work on issues", "implement the spec", "start coding", or wants agents to build from planned issues.

Discover implicit architectural decisions and spec-worthy subsystems in an existing codebase. Use when the user says "discover architecture", "what decisions exist in this code", "bootstrap ADRs", or wants to reverse-engineer design artifacts from code.

Create a new Architecture Decision Record (ADR) using MADR format. Use when the user wants to document an architectural decision, says "create an ADR", "we need an ADR for", or discusses a decision that should be recorded.

Comprehensive audit of design artifact alignment across the project. Use when the user says "audit the architecture", "full drift report", or wants a thorough review of spec compliance and ADR adherence.

Cut a release on GitHub or Gitea — the forge-level Release object (notes + assets) that sits on top of a git tag, NOT just the tag itself. Use this skill whenever the user says "cut a release", "cut a tag", "tag a release", "ship it", "publish v1.2.0", "do a release", or "draft release notes", and especially right after a PR is merged to the default branch when it's time to ship. The skill auto-discovers the forge from the git remote (github.com → GitHub, anything else → probe for Gitea/Forgejo), verifies CI is green on the merge commit before publishing, figures out the next semver tag from the repo's existing tag convention and the commits since the last tag, then creates an annotated tag and a Release with notes. Works for single-version repos and monorepos with per-component tags (like this one: `<skill-name>-vX.Y.Z`). Reach for this even if the user only says "tag" — confirm whether they want a bare tag or a full release.

Curate, consolidate, and restyle the StumpCloud Runbooks wiki in Outline (outline.stump.rocks) against the repo as source of truth. Use this skill whenever the user wants to review/clean up the wiki, consolidate or reorganize runbooks, fix stale or duplicated docs, reconcile Outline against the repo (ADRs, inventory, docs/), restructure the doc tree into hierarchy-native nodes, or apply the domain color + topical icon scheme to wiki nodes. Trigger on phrases like "audit the runbooks", "clean up the wiki", "consolidate the Outline docs", "the wiki is out of date", "reorganize/restyle the Runbooks collection", or "color and icon the docs". This is the governance/curation counterpart to the `stumpcloud-omg` skill (which files individual incidents); use that for postmortems, this for whole-collection curation. Always propose a consolidation plan and get approval before any destructive merge/move/delete.

Refresh the Miatrix indexer API token in Prowlarr by logging into Miatrix via browser automation and extracting the current API key. Use this skill whenever Miatrix keeps re-downloading the same episodes or shows, when Prowlarr reports Miatrix indexer errors or failures, or when a Miatrix API key rotation is suspected. The skill handles the full workflow automatically: gathers credentials, logs into Miatrix, grabs the API key from the profile page, and updates Prowlarr's indexer config — no manual steps required.

Generate high-fidelity UI mockup PNGs for any project by calling Gemini's image model through LiteLLM. Use this whenever the user asks to mock up, generate, regenerate, or update a UI screen, page, modal, or component — login screens, dashboards, settings panels, wizards, admin views, anything with a visual surface. The skill reads the project's visual identity from its `CLAUDE.md` at runtime, frames every output in macOS Safari chrome with a project-appropriate URL, saves to a stable filename so reruns overwrite cleanly, and scans in arrears for older mockups in the same directory that may be stylistically out of date. Prefer this over the bundled `mockup-generator` skill when LiteLLM is the gateway (env vars `OPENAI_BASE_URL` and `OPENAI_API_KEY` live in the user's login shell) and when project visual identity should drive style rather than light-mode DaisyUI defaults.

Generate a high-fidelity, durable retirement-plan.html from a Claude Project's financial documents and lifestyle assumptions. Triggers when the project name suggests retirement focus (retire, retirement, FIRE, early retire, freedom), the user invokes /retirement-plan or asks to build/update/refresh the plan, new financial documents are uploaded, the user mentions a money event (inheritance, RSU vest, property sale, large bonus, paid-off mortgage), or an existing retirement-plan.html is older than 3 months OR built from documents older than 6 months. Produces a single self-contained HTML file with five tabs (Execution plan, Income reality, Big purchases, At retirement, Lifetime projection), inline SVG chart, and interactive knobs. Re-triggers read the prior artifact as canonical state and apply deltas rather than starting over.

File GitHub issues against joestump/claude-skills when another skill in this repo hits friction during a run. Other skills in this repo delegate their self-evaluation reporting to this skill rather than implementing their own filing logic. Triggers when another skill explicitly invokes self-report after detecting that its trip thresholds were exceeded (tool-call budget, repeated bug retries, material assumptions, render integrity issues, user pushback in same turn), or when the user explicitly invokes /self-report. If multiple skills from this repo ran in the same session and each independently tripped, file one issue per skill — never bundle reports for different skills into a single issue. Each issue is labeled with both skill-self-report and skill:<skill-name> so they can be filtered per-skill on the issues tab. Issue bodies must never contain user data, account balances, names, or document contents — only meta-signals about how the run went.

Write idiomatic Go following Google/Uber style guides. Use for Go code generation, reviews, or refactoring. Emphasizes error handling, testing, concurrency patterns.

Create technical specifications with spec.md (requirements) and design.md (implementation). Use when asked to write technical specs, design documents, system designs, or when user mentions "spec", "technical design", or "architecture document".

Security-focused code and infrastructure review. Use when reviewing code, PRs, Terraform, or when user asks about security. Checks for common vulnerabilities, secrets, misconfigurations.

Write production-ready Terraform following HashiCorp best practices. Use for infrastructure code, module design, or Terraform reviews. Emphasizes state management, security, reusability.