19 lines
1.5 KiB
Markdown
19 lines
1.5 KiB
Markdown
# Quick Handoff Protocol
|
|
|
|
When VS Code or the session goes down, follow these steps to get back on track quickly:
|
|
|
|
1. **Read the daily snapshot** in `docs/automation/daily/`. Each file is named `YYYY-MM-DD-summary.md` and contains the commits and file diff stats for that date.
|
|
2. **Skim the rolling commit log** inside `docs/automation/commit-log/`. Every commit appends its metadata and `git diff --stat` output, so you can trace changes even without the original editor context.
|
|
3. **Check the docs index** (`docs/00-INDICE-MASTER-NETGESCON.md`) after the logs to jump to the detailed manuals that were touched.
|
|
4. **Need command history?** The last commands are stored in `~/.bash_history` and mirrored into `docs/automation/daily/<date>-commands.txt` whenever you run the daily snapshot script.
|
|
5. **Before resuming work**, write a short note in the current day summary (under "Notes") about what you plan to do next. That note is the breadcrumb for the next teammate.
|
|
|
|
If you are a new assistant:
|
|
|
|
- Start with yesterday's daily summary, then today's commit log entries.
|
|
- Cross-reference any unfamiliar files in the docs index.
|
|
- Update the end of the current day's summary with what you accomplished.
|
|
- Mention any open questions in `docs/automation/daily/<today>-summary.md`.
|
|
|
|
> Remember: these files are intentionally lightweight markdown that survive crashes and can be versioned with the repository. Keep adding to them so the next "alter ego" never has to start from scratch.
|