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.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.
Tester
Utilisation de « session-handoff ». Prepare a handoff for a feature with passing unit tests and unfinished integration tests.
RĂ©sultat attendu:
- 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.
Utilisation de « session-handoff ». Summarize an interrupted investigation of duplicate background jobs.
RĂ©sultat attendu:
- 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.
Audit de sécurité
SûrAll 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.
Facteurs de risque
Partager et citer ce rapport
Partagez le rapport d’évaluation versionné, le badge neutre, la carte intégrable et les citations. Skillstore présente les preuves sans décider si ce Skill est sûr.
Copier le lien du rapport
https://skillstore.io/skills/alapha888-session-handoff/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/alapha888-session-handoff?utm_source=security_passport_badge)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>Carte intégrable
<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>Citations académiques (APA · BibTeX · CFF)
Citation APA
alapha888. (2026). session-handoff security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-session-handoff/audits/1Citation 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"
Comparer les variantes
3 variantes installablesChaque auteur reste un skill installable distinct. La variante recommandée est classée selon les preuves Skillstore.
Pourquoi cette variante est première
agentkitco-session-handoff
2026-10-22
alapha888-session-handoff
2026-10-06
softaworks-session-handoff
2026-09-09
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
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.
Essayez ces prompts
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.
Bonnes pratiques
- 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.
Éviter
- 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.
Foire aux questions
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?
Détails du développeur
Auteur
alapha888Licence
MIT
RĂ©vision Skillstore
r1
Avis de version
L’auteur n’a déclaré aucune version.
DĂ©pĂ´t
https://github.com/alapha888/session-handoff-kit/tree/bf9c17a685169609e3574ab10a8cfab49b1781ba/RĂ©f
891cdfa4e0612e161319701fa5315ae09a811eb5
RĂ©cence de maintenance
06/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đź“„ context-hygiene-checklist.md
đź“„ handoff-template.md
đź“„ LICENSE
đź“„ README.md
đź“„ SKILL.md