session-handoff
Preserve Coding Progress Across Agent Sessions
Ending a long coding session can lose decisions, verified progress, and unresolved tasks. This skill organizes that context into a structured note for the next session.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "session-handoff" from https://skillstore.io/skills/alapha888-session-handoff.md and its manifest at https://skillstore.io/api/skills/alapha888-session-handoff/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «session-handoff». Prepare a handoff for a feature with passing unit tests and unfinished integration tests.
Ожидаемый результат:
- Goal: Complete the account settings update.
- Current state: Input validation is implemented; the targeted unit tests passed.
- Decision: Reuse the existing validation helper to keep behavior consistent.
- Open task: Agent owns integration coverage; verify valid and invalid submissions.
- Next action: Add the missing invalid-submission integration test.
Использование «session-handoff». Summarize an interrupted investigation of duplicate background jobs.
Ожидаемый результат:
- Goal: Prevent duplicate jobs after retries.
- Current state: A regression test reproduces duplicate insertion; the cause remains unverified.
- Rejected approach: Increasing retry delays did not resolve the failure.
- Open task: Agent investigates transaction boundaries; verify with the regression test.
- Next action: Inspect the enqueue operation used by the failing test.
- Watch-out: Do not change the configured retry limit during this investigation.
Аудит безопасности
БезопасноAll 17 static findings are false positives: Markdown formatting, read-only Git inspection, or illustrative handoff content. The environment-file reference assigns a human configuration task without reading, exposing, or transmitting credentials. No evidence found of prompt injection or data exfiltration; session resets serve the stated handoff workflow.
Факторы риска
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/alapha888-session-handoff/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/alapha888-session-handoff?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/alapha888-session-handoff?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alapha888-session-handoff/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/alapha888-session-handoff.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Академические ссылки (APA · BibTeX · CFF)
Цитата APA
alapha888. (2026). session-handoff security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-session-handoff/audits/1Цитата BibTeX
@techreport{alapha888-alapha888-session-handoff-2026,
author = {alapha888},
title = {session-handoff security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/alapha888-session-handoff/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "session-handoff security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "alapha888"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/alapha888-session-handoff/audits/1"
identifiers:
- type: other
value: "skillstore:alapha888-session-handoff:audit:1"
description: "Skillstore immutable audit report identifier"
Сравнить варианты
3 устанавливаемых вариантовНавык каждого автора остаётся отдельным устанавливаемым вариантом. Рекомендуемый вариант ранжируется по данным Skillstore.
Почему этот вариант первый
agentkitco-session-handoff
2026-10-22
alapha888-session-handoff
2026-10-06
softaworks-session-handoff
2026-09-09
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Pause Feature Development
Record implemented behavior, changed files, and the next verification step before ending a coding session.
Transfer Debugging Work
Document failing checks, discarded hypotheses, and remaining tasks when another engineer takes over an investigation.
Resume Repository Maintenance
Capture migration dependencies, verified fixes, and unresolved release tasks before moving to a fresh agent session.
Попробуйте эти промпты
Create a session handoff note for the current task. Include the goal, verified progress, changed files, unresolved tasks, and one next action.
Inspect Git status and diff statistics before drafting the handoff. Separate passing checks from unverified assumptions and list exact changed files.
Prepare a debugging handoff with the current failure, rejected approaches, relevant symbols, task owners, verification criteria, and the first diagnostic action.
Use the handoff template before a context reset. Record architectural decisions, dependencies, human approvals, unverified assumptions, and one precise next action. Exclude secret values.
Лучшие практики
- Inspect current workspace changes and record exact verification results before drafting the note.
- Use real file paths and symbols; assign each unresolved task an owner and a completion check.
- Save the note before resetting context, exclude secret values, and keep the next action specific.
Избегать
- Paste the full conversation instead of a focused handoff.
- Mark work complete without running checks or labeling unverified assumptions.
- Omit rejected approaches or finish with a vague continuation request.
Часто задаваемые вопросы
When should I create a handoff note?
Which coding agents are mentioned?
Does the skill preserve running processes?
How does it distinguish facts from assumptions?
Does a handoff replace commits or tickets?
Should I include credentials in the note?
Сведения для разработчиков
Автор
alapha888Лицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Репозиторий
https://github.com/alapha888/session-handoff-kit/tree/bf9c17a685169609e3574ab10a8cfab49b1781ba/Ссылка
891cdfa4e0612e161319701fa5315ae09a811eb5
Актуальность поддержки
06.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов