skills/handoff-list/SKILL.md
Use when viewing available handoff documents — lists active and archived handoffs with their status, date, topic, and branch
npx skillsauth add lucianghinda/superpowers-ruby handoff-listInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Display all available handoff documents, both active (unrestored) and archived (consumed). Helps you decide which handoff to resume or review.
Announce at start: "I'm using the handoff-list skill to show available handoffs."
superpowers-ruby:handoff-resume to see what's available# Active handoffs
ls docs/handoffs/*.md 2>/dev/null
# Archived handoffs
ls docs/handoffs/_archive/*.md 2>/dev/null
For each file found, read the YAML frontmatter to extract: created, topic, branch, trigger, restored.
Present results with active (unrestored) handoffs first, then archived, sorted by date descending:
## Active Handoffs
| Date | Topic | Branch | Trigger |
|------|-------|--------|---------|
| 2026-04-14 | handoff-skill | lg/handoff | manual |
## Archived Handoffs
| Date | Topic | Branch | Trigger | Restored At |
|------|-------|--------|---------|-------------|
| 2026-04-13 | auth-refactor | fix/auth | compact | 2026-04-13T15:30:00 |
If no handoffs exist:
No handoff documents found in docs/handoffs/ or docs/handoffs/_archive/.
Use `/superpowers-ruby:handoff` to create one.
If active handoffs exist, offer:
"Would you like to resume from one of the active handoffs? Use
/superpowers-ruby:handoff-resume."
development
Use when writing, reviewing, or debugging pure Ruby code — idiomatic patterns, modern 3.x+ features (pattern matching, Data.define, endless methods), error handling conventions (raise vs fail, result objects), memoization, and performance idioms. For Rails use rails-guides. For testing use minitest. For code style use sandi-metz-rules.
testing
Official Rails documentation. Use when asked about any Rails-specific topic including ActiveRecord, routing, controllers, views, mailers, jobs, Action Cable, Action Text, Active Storage, migrations, validations, callbacks, associations, caching, security, or internals.
tools
--- name: ruby-upgrade description: Use when upgrading the Ruby interpreter version of a Bundler/Rails app — especially "upgrade to Ruby 4", "bump Ruby to 4.0", "audit Ruby 4 compatibility", "what breaks on Ruby 4", or a specific target like "Ruby 4.0.5". Triggers on Ruby-major risk symptoms: CGI.parse/CGI::Cookie removal, Net::HTTP implicit Content-Type dropped, demoted default gems (ostruct/logger/benchmark/irb), SortedSet, Set#inspect changes, native-extension recompile crashes, openssl 4 pin
development
Use when stuck after multiple debug attempts and want to escalate to a stronger one-shot model (GPT-5 Pro, Opus, Gemini Pro) — packages a self-contained "oracle prompt" with Ruby/Rails project briefing, verbatim error, what-was-tried, constraints, and just-enough attached files. Triggers include "ask the oracle", "write a letter to GPT-5", "I'm stuck, draft a prompt for another model", "/tmp/letter.md".