Menu
Updates agentic memory files (activeContext, systemPatterns, productContext) and project docs with work done in the current session. Use at the end of a development session to keep memory in sync with the codebase.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | session-update |
| description | Updates agentic memory files (activeContext, systemPatterns, productContext) and project docs with work done in the current session. Use at the end of a development session to keep memory in sync with the codebase. |
This skill closes out a development session by syncing memory files, documentation, and heuristic context with the work completed. It ensures the next agent session starts with accurate context.
/hyper-session-update.Review Session Work
task.md) to identify what was accomplished.Update Product & Design Specs
spec/compiled/SuperPRD.md.docs/DESIGN.md.spec/compiled/architecture.yml. Use the deterministic scripts or /hyper-discover//hyper-audit for that.Update Agentic Memory
activeContext.md: Update with current focus, recent changes, and immediate next steps.systemPatterns.md: Add new code patterns, idioms, or architectural structures discovered. Remove replaced ones.productContext.md: Update if there are new product-level decisions or evolved features.Update Rules (if needed)
.agents/rules/ (or create a new rule file for major topics).Commit
chore: update memory commit.Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.
Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.
Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.
Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.
Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.
Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.