When to use it

Use solutions after resolving a nontrivial project problem, or when symptoms resemble something you have solved before. This is memory about how the project works: a flaky test’s cause, a migration failure, or a configuration interaction.

How it works

Figure 01

Keep the fix and the evidence that it worked.

  1. Verify

    Establish the cause and check the fix.

  2. Record

    Save symptoms, failed attempts, and verification.

  3. Recheck

    Compare the saved solution with current code before reuse.

Result.ai/memory/SOLUTIONS.md
Symptoms help retrieve an old solution. Rechecking prevents yesterday’s fix from becoming an unchecked assumption today.

The skill records symptoms, relevant context, failed attempts, the fix, the diagnosed cause, and how the result was verified in .ai/memory/SOLUTIONS.md. Symptoms make the entry useful even when you do not remember the original diagnosis.

When a similar problem returns, it checks the stored fix against the current code before applying the old explanation. During an explicit refresh, it can propose keeping, updating, merging, or retiring entries as the project changes.

An example request

Ask your agent

“Save the connection-pool fix as a solution. Include the timeout symptoms, the two approaches that failed, and the load test that verified the change.”

This illustrates a request you can adapt; it is not a transcript of a completed run.

A later investigation can start from a tested explanation and avoid repeating dead ends, while still checking whether the explanation fits today’s code.

Install and use

The skill’s identifier is solutions. It ships in the session-memory plugin. In Claude Code, first add the Overclock marketplace, then install the package:

/plugin install session-memory@overclock

For a standalone installation, keep the skill directory and its bundled resources together. The repository also includes per-skill Codex metadata. Read the full skill instructions for its exact workflow and supporting files.

What to keep in mind

Unverified guesses should not be saved as proven fixes. If the evidence is limited, the record needs to retain that limitation.

Corrections about how the agent should behave belong in lessons-learned. Solutions stores diagnosed project problems and does not run background cleanup or automatic commits.

  • Lessons learned — Turn a correction into a reusable lesson, and keep repeated lessons up to date.
  • Debugging discipline — Build a useful observation loop for a bug that resists straightforward reproduction.