engram-mistakes

Retrieve recorded project mistakes before proposing a related change.

Prerequisites

Use a reviewed compatible engramx installation and an indexed project. Resolve the project path under the workspace rules before a file operation. If the CLI or graph is unavailable, explain the limitation and fall back to direct source inspection; do not silently claim success.

Invocation

engramx mistakes --project . --limit 20

This command is source-inspected against the captured engine CLI, not executed during the documentation review.

Interpretation

Compare returned records with the current source and task. Optionally narrow with --since DAYS. A missing record means no matching indexed evidence was returned; it does not prove an approach is safe.

Boundaries

Do not invent prior attempts, treat every mined bug-fix message as a confirmed failure analysis, or claim that an instructional skill installs a hook automatically.

The engine stores its graph under the project .engram directory. Graph text enters the agent context, so the agent provider policy still applies. Optional engine integrations and update checks have separate network behavior; this skill does not guarantee zero egress.

Reference material

Files under references/ explain trigger intent, output interpretation, evaluation, and source-checked limitations. They are guidance for the inspected engine revision; recheck supported options when upgrading.