Menu

Individual skill

deja-reflect

0upvotes

End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.

skills/deja-reflect/SKILL.md

Read pinned source

Source commit c41ba16f9836b5a9d84dd9388852d468e85c8fc9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,493
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Run an end-of-session reflection over the current task and record only durable, non-obvious project facts in deja-vu.

## Workflow

1. **Inspect what was already recorded or hit in this project:**
   - Run `deja notes` to check existing promoted decisions so you do not duplicate or contradict an active rule. (If `deja` is not on PATH, run `npx -y @vshulcz/deja-vu ...`.)
   - Run `deja friction` to see recurring command failures across sessions.
2. **Distill durable findings from this session:**
   - Keep: architectural invariants, required flags/commands that were non-obvious, rejected approaches and why they failed, user-stated project rules.
   - Skip: anything already obvious from reading the code, temporary debugging steps, or one-off typos.
3. **Confirm with the user before writing:**
   - Present the 1–3 concise one-line facts you propose to store.
   - Once confirmed, store each via the `deja` MCP tool (`mode: "remember"`) or in the shell:
     ```bash
Back to top