end

Included with Lifetime

$97 forever

End session, save progress, create handoff. Triggers: wrap up, done for today, end session, save my work, save progress, close out. Runs health checks and captures resume point.

General

What this skill does


# Handoff End

ultrathink

<role>
Senior engineer closing a shift. Precise state capture: exact errors, specific file:line references, honest severity. Never vague, never ask the user.
</role>

## Pre-loaded State

### state.json
!`cat .handoff/state.json 2>/dev/null || echo "{}"`

### Git
!`git status -s 2>/dev/null`
!`git log -5 --format='%h %s' 2>/dev/null`

## Steps

1. **Bootstrap**: Create `.handoff/` if missing. Write `.handoff/.gitignore` with `state.json` and `sessions/` if missing.
2. **Health checks**: Detect package manager from lockfile (`bun.lock` -> bun, `package-lock.json` -> npm, `pnpm-lock.yaml` -> pnpm, `yarn.lock` -> yarn, `Cargo.lock` -> cargo, `go.sum` -> go). Run build, test, lint. Record pass/fail/null for each.
3. **Analyze session** from conversation + git log. DO NOT ask the user:
   - Severity: CRITICAL (build failing), IN_PROGRESS (tests failing, uncommitted work, mid-feature), READY (all green)
   - Done: commits and features completed `[{"description": "string", "ref": "hash"}]`
   - Blockers: external deps, missing credentials, pending decisions
   - Watch out for: gotchas, workarounds, edge cases
   - Resume: specific `file:line action`, files to read first, context
4. **Write state.json** via atomic write (`.tmp.$$` then `mv`):
   ```json
   {
     "severity": "READY|IN_PROGRESS|CRITICAL",
     "health": {"build": "pass|fail|null", "tests": "pass|fail|null", "lint": "pass|fail|null"},
     "resume": {"next": "file:line action", "files": ["string"], "context": "string"},
     "done": [{"description": "string", "ref": "string"}],
     "blockers": ["string"],
     "watch_out_for": ["string"],
     "hostname": "string",
     "session_id": "string",
     "timestamp": "ISO"
   }
   ```
5. **Create tasks**: Blocker tasks (metadata: `blocker: true, handoff: true`) + resume task blocked by blockers (metadata: `resume: true, handoff: true`).
6. **Output**:
   ```
   HANDOFF COMPLETE
   Severity: [emoji SEVERITY]
   Health: build=[status] tests=[status] lint=[status]
   Resume: [next action]
   Safe to end session.
   ```

## Severity

| Level | Condition |
|-------|-----------|
| CRITICAL | Build failing, prod down, security issue |
| IN_PROGRESS | Tests failing, uncommitted work, mid-feature |
| READY | All green, clean state |

## Anti-Patterns

DON'T: Skip health checks. Write vague resume ("keep working on X"). Leave READY with failing tests.
DO: Exact error messages. Specific file:line in resume. Honest severity.

## Gotchas

- Atomic write (`mv .tmp.$$ state.json`) fails silently if `.handoff/` doesn't exist yet. Always bootstrap the directory before writing.
- `jq` is an allowed tool but not guaranteed installed. If `jq` is missing, fall back to writing JSON directly from the shell or use Write.
- Health checks can hang indefinitely on projects with interactive test watchers (Jest `--watch`, Vitest default). Always pass `--watchAll=false` or `--run` flags.
- Setting severity to READY when there are uncommitted changes is a lie. Uncommitted work means IN_PROGRESS, even if build/test/lint all pass.
- The `session_id` field is only useful for `--resume` on the same machine. If the user switches devices, the resume hint is misleading.

Files: 1

Size: 3.7 KB

Complexity: 12/100

Category: General

Source: https://github.com/ramonclaudio/skills/tree/main/plugins/handoff/skills/end

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts