Menü
Compact the current conversation into a handoff document for another agent to pick up.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Author local Maestro iOS-Simulator E2E flows for the Kata Code mobile app using the reusable TS orchestrator and Kata-specific flows. Use when adding or updating flows under mobile-e2e/.
Assess and selectively port changes from the upstream T3 Code fork (pingdotgg/t3code) into Kata Code. Use whenever the user wants to review what upstream has done, assess the diff, decide what to bring in, triage upstream commits, plan a vendor-pull, run an upstream scan, or figure out which upstream changes are worth porting. Covers scanning upstream since the last baseline, grouping commits by effort and risk, recommending Port/Skip/Watch per change, and re-implementing chosen changes as fork-original commits with Kata branding applied from the start.
Use this skill for multi-step, spec-driven, or acceptance-gated implementation work that should move through Plan, Build, and Verify phases.
Author local Playwright Electron E2E tests for Kata Code using the reusable harness and Kata-specific flows. Use when adding or updating tests under e2e/.
Use when preparing, packaging, tagging, or publishing Skiller Desktop releases, including GitHub release CI, macOS code signing, notarization, release secrets, and desktop version bumps.
Validate Kata Code nightly releases on macOS with the @Computer plugin. Start and update the nightly app, use its New Project flow to create a timestamp-suffixed nightly UAT project under `/Volumes/EVO/dev`, then execute explicit acceptance criteria for a Codex GPT-5.4-Mini chat, Browser and Files panels, and git commit flow; capture criterion-level screenshots and write an evidence-linked report in the created project. Use when validating or documenting the Kata Code nightly release flow.
| name | handoff |
| description | Compact the current conversation into a handoff document for another agent to pick up. |
| argument-hint | What will the next session be used for? |
| disable-model-invocation | true |
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save local to the project at docs/handoff/session-<timestamp>.md
Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
Do not duplicate content already captured in other local (e.g., ./docs bundle) or online artifacts (e.g., Linear of GitHub issues). Reference them by path or URL instead.
Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
