lucianghinda/handoff-resume
skills/handoff-resume/SKILL.md
Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context
$ install --global
skillsauthnpx skillsauth add lucianghinda/superpowers-ruby handoff-resumeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 2:15 AM171.9s1 file scanned
SKILL.md
- name:
- handoff-resume
- description:
- Use when starting a new session and wanting to continue from a previous handoff — reads the latest unrestored handoff document and restores session context
Handoff Resume
Overview
Resume work from a previously created handoff document. Finds the latest unrestored handoff, reads it, marks it as consumed, archives it, and sets up the session to continue from where the previous session left off.
Core principle: Read the handoff, understand the context, then continue from Next Steps.
Announce at start: "I'm using the handoff-resume skill to restore session context."
When to Use
- Starting a new session to continue previous work
- After a session was ended without completing work
- When a colleague or agent left a handoff for you
- When you see handoff documents exist in
docs/handoffs/
Don't use when:
- Context was just compacted (the
PostCompacthook handles this automatically) - There is no handoff document to resume from
The Process
Step 1: Find Unrestored Handoffs
# Look for handoff files with restored: false
ls docs/handoffs/*.md 2>/dev/null
Read each file's frontmatter and filter for restored: false. Sort by created date, newest first.
Step 2: Select Handoff
If one unrestored handoff exists: Use it automatically.
If multiple unrestored handoffs exist: Present them and ask which to resume:
Found multiple unrestored handoffs:
| # | Date | Topic | Branch |
|---|------|-------|--------|
| 1 | 2026-04-14 | handoff-skill | lg/handoff |
| 2 | 2026-04-13 | auth-refactor | fix/auth |
Which handoff should I resume from?
If no unrestored handoffs exist: Check the archive:
ls docs/handoffs/_archive/*.md 2>/dev/null
If archived handoffs exist, list them and offer to re-open one. If none exist at all, inform the user.
Step 3: Read and Present
Read the full handoff document. Present a summary:
Resuming from handoff: <topic>
- Branch: <branch>
- Created: <date>
- Goal: <goal summary>
- Next steps: <count> items
- Files to read: <count> documents
Step 4: Mark as Restored and Archive
Update the handoff file's frontmatter:
- Set
restored: true - Add
restored_at: <ISO 8601 UTC timestamp>
Move the file to docs/handoffs/_archive/.
Step 5: Restore Context
- Read the Files to Read section first — open each referenced plan, spec, or doc
- Review the Current State and Key Decisions — understand what was done and why
- Check Modified Files — run
git statusto see if the working tree matches expectations - Note Failed Approaches — avoid repeating what didn't work
- Continue from Next Steps — start working on the first item
If any sections contain <!-- to be enriched by LLM --> markers (from a hook-generated handoff), fill them in from available context before proceeding.
Pairs With
- superpowers-ruby:handoff — Creates the handoff documents this skill resumes from
- superpowers-ruby:handoff-list — View all available handoffs before choosing
Related Skills
lucianghinda/ruby
development
VerifiedTrustedCommunity
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.
317SKILL.mdUpdated Apr 25, 2026
lucianghinda/rails-guides
testing
VerifiedTrustedCommunity
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.
316SKILL.mdUpdated Apr 25, 2026
lucianghinda/skills/ruby-upgrade
tools
VerifiedTrustedCommunity
--- 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
306SKILL.mdUpdated May 29, 2026
lucianghinda/consulting-an-oracle
development
VerifiedTrustedCommunity
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".
306SKILL.mdUpdated May 9, 2026