etanhey/catchup
skills/golem-powers/catchup/SKILL.md
Use when returning to work after any break — auto-detects depth. Short break (hours): reads only uncommitted changes. Long break (48h+) or context overflow: reads all branch changes vs main. Covers catchup, context recovery, refresh, rebuild understanding. NOT for: mid-task exploration (use Read/Grep directly).
$ install --global
skillsauthnpx skillsauth add etanhey/golems catchupInstall 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: Apr 17, 2026, 12:12 PM18.2s3 files scanned
SKILL.md
- name:
- catchup
- description:
- Use when returning to work after any break — auto-detects depth. Short break (hours): reads only uncommitted changes. Long break (48h+) or context overflow: reads all branch changes vs main. Covers catchup, context recovery, refresh, rebuild understanding. NOT for: mid-task exploration (use Read/Grep directly).
Skill: Catchup (Context Recovery)
Auto-detects break length and adjusts depth. Short break = uncommitted changes only. Long break = full branch diff vs main.
When to Use
- Returning after ANY break (hours or days)
- Context window overflow — need to rebuild understanding
- Before committing — review what's staged
- Reviewing what's been done on a feature branch
Auto-Detect Mode
Check both signals to pick the right mode:
# 1. Check uncommitted changes
git status --short
# 2. Check branch commit count
git log --oneline main...HEAD 2>/dev/null | wc -l
| Uncommitted changes? | Branch commits? | Mode | |---------------------|-----------------|------| | Yes | Few (0-3) | Quick — read uncommitted only | | No | Many (4+) | Full — read all branch changes | | Yes | Many (4+) | Full — read everything | | No | None | Nothing to catch up on |
User can override: /catchup quick or /catchup full
Quick Mode (short break, uncommitted changes)
Step 1: Get Status
git status --short
Status codes:
M— Modified (staged)M— Modified (unstaged)MM— Modified (both)A— Added (staged)??— Untracked
Step 2: Read Modified Files
Read only files with M status. Skip untracked (??) unless relevant.
Step 3: Quick Summary
- Files currently being edited
- What changes are in progress
- Ready to continue or need clarification
Full Mode (long break, full branch context)
Step 1: Get Changed Files
git diff --name-only main...HEAD
Step 2: Read All Changed Files
Read in dependency order:
- Schema/database files (
schema.ts,convex/,prisma/) - Config files (
package.json,tsconfig.json,.env.example) - Server/API files (
actions/,api/,server/) - Components/UI files (
components/,app/) - Tests (
tests/,*.test.ts)
Step 3: Full Summary
- What feature/fix is being worked on
- Current state of implementation
- What appears to be left to do
Tips
- If full mode shows 50+ files, start with quick mode first
- Check
git log main...HEAD --onelinefor commit history context - Look for TODO/FIXME comments to understand remaining work
- Combine with
git diffto see actual line changes
Related Skills
etanhey/writing-skills
development
VerifiedTrustedCommunity
Create, edit, and verify golem-powers skills using the standard SKILL.md structure, workflow files, adapters, templates, and eval fixtures. Use for new skills, structural edits, workflows/adapters, and pre-deploy validation. NOT for invoking existing skills, superpowers skills, or skill-creator agent workflows.
3SKILL.mdUpdated Jun 4, 2026
etanhey/video-extract
testing
VerifiedTrustedCommunity
Extract structured knowledge from any video source — YouTube URLs or local screen recordings. YouTube → gems workflow (yt-dlp transcript → keyword hotspots → frame extract → brain_digest → structured gems). Screen recordings → QA workflow (reuses /qa-video stalker pipeline). Use when user shares a YouTube link wanting deep extraction with frames, shares a .mov/.mp4 for QA processing, says "extract from video", "video gems", "process this recording", or mentions gem extraction from video content.
3SKILL.mdUpdated Jun 4, 2026
etanhey/monitor-loop
testing
VerifiedTrustedCommunity
Use when running or reviewing any recurring monitor loop for merge queues, worker queues, collab tails, or agent completion. Enforces drive-to-completion ticks: every tick must query live state with `!`, classify whether real progress happened, and then dispatch, verify-and-decrement, or escalate-park. Triggers on: monitor loop, /loop, recurring tick, keep monitoring, silent autonomous, merge gate, blocked review, no-progress loop.
3SKILL.mdUpdated Jun 4, 2026
etanhey/mehayom
tools
VerifiedTrustedCommunity
MeHayom freelance client management — daily updates, decision tracking, time logging. Use when drafting Yuval updates, logging scope changes, tracking hours, or any MeHayom client communication. Triggers: 'draft Yuval update', 'client update', 'daily update', 'log decision', 'track time', 'mehayom'.
3SKILL.mdUpdated Jun 4, 2026