القائمة
Writes a structured session handoff so a fresh agent can continue without losing thread
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/CleanExpo/Unite-Group --skill handoffيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
The authoritative environment-variable registry for the Unite-Group Nexus. Use whenever adding, reading, renaming, or debugging an env var or secret — new integration config, a `process.env.X` read, an auth/OAuth wiring, a cron secret, a "which variable holds this" question, or a "works locally but not in prod" symptom. Also use before pinning any variable name in code, and when reconciling the two credential planes (Vercel prod vs the local hermes fleet). Prevents the `APIFY_API_KEY` vs `APIFY_API_TOKEN` class of drift.
Create, verify, and promote Supabase schema changes via database branches. Every schema change/migration must be validated on a Supabase database branch before prod (see CLAUDE.md line 44).
Verify production Supabase schema before shipping code that touches it. Use BEFORE writing or reviewing ANY code that reads or writes a Supabase table in the Nexus — new queries, inserts, updates, CHECK-constrained values, RLS-dependent reads, cron data access — even one-line changes and even when the table "obviously" exists. Also use immediately when a query fails with "column does not exist", when inserts appear to succeed but produce no rows, or when generated TypeScript types disagree with runtime behaviour.
| name | handoff |
| description | Writes a structured session handoff so a fresh agent can continue without losing thread |
Different from /compact (which compresses context):
Type: /handoff [optional: brief description of what was happening]
The agent writes a handoff document to: ~/.hermes/handoffs/YYYY-MM-DD-HH-MM.md
Structure:
# Handoff — [date time AEST]
## What was being worked on
[1 paragraph — specific task, not vague]
## Current state
- What's DONE (committed/verified)
- What's IN PROGRESS (started but not committed)
- What's BLOCKED and why
## Files modified this session
[list with one-line description of change per file]
## The next agent should
[Numbered list — specific actions, not "continue the work"]
## Context the next agent needs
[Key facts, decisions made this session, any gotchas discovered]
## Commands to run first
```bash
# Verify state before continuing
[e.g. pnpm type-check, git status, etc.]
[Anti-patterns or dead ends discovered this session]
## Usage patterns
### Handing off to prototype
"I've drafted the spec, /handoff to prototype"
→ Writes handoff → prototype agent reads it → picks up from spec
### Handing off mid-feature
"/handoff — auth middleware half-done"
→ Writes handoff → fresh agent knows exact stopping point
### Cross-session (close laptop)
"/handoff end of day"
→ Writes handoff → tomorrow's agent reads it at session start
## Integration with soul.md
At session start, Hermes agents check ~/.hermes/handoffs/ for the most recent handoff.
If found (< 24 hours old), inject it alongside soul.md as Tier-0 context.