Captures reusable knowledge after work is done — learnings from feedback or failures, resolved bugs (symptom, root cause, prevention), and recurring code patterns — into the project's persistent memory file. Use after feedback, a non-trivial bug fix, a failed attempt, or the third repetition of a pattern.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Every problem solved should leave something behind that makes the next one cheaper. This skill records it in the one place the agent will actually read next session.
vibe-decision-journal, which keeps ADRs in the repo)Write to the memory file the current agent loads automatically. A separate LEARNINGS.md that nothing loads is write-only.
| Agent | Loaded automatically |
|---|---|
| Claude Code | CLAUDE.md (project) or auto-memory, if enabled |
| OpenAI Codex | AGENTS.md |
| Gemini CLI | GEMINI.md, or the built-in memory tool |
| Shared across tools | AGENTS.md, imported or referenced from the others |
Keep the always-loaded file short. Put long entries in docs/learnings/ (bugs, patterns, learnings) and add a one-line pointer to them in the memory file.
- **[Pattern name]**: [actionable rule]. Applies when: [context]. Evidence: [what happened].
Be actionable and specific. Not "be careful with concurrency" but "run the race detector before committing code that touches sessionCache."
### [Category]: [short description] ([date])
Symptom: [what was observed]
Root cause: [the actual problem]
Why hard to find: [what misled the investigation]
Fix: [what changed] — Prevention: [test, lint rule, or guard added]
Files: [paths]
Categories: Concurrency, State, Validation, Integration, Environment, UI.
### [Pattern name] — [category]
When to use: [situation]
Canonical example: [file:line]
Anti-pattern: [the common mistake]
Point to the canonical implementation in the codebase instead of copying code into the memory file.
docs/learnings/archive.md.Trigger: [what prompted this]
Entries:
Saved to: [file path(s)] Active learnings: X/30
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Validates completed work against defined acceptance criteria. Use after completing a task that has specific success criteria defined in issues, specs, or task descriptions.
The English summary is being prepared. Showing the original description.
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests. Use after happy-path tests exist and before claiming coverage is complete, when requirements lack tests, or before a security review.
The English summary is being prepared. Showing the original description.
Catches shortcuts and reward hacking — weakening or deleting tests to make them pass, hard-coding expected outputs, silently dropping requirements, or claiming work is done without running it. Use before declaring a task complete and whenever a test or requirement feels like it's in the way.
The English summary is being prepared. Showing the original description.
Safely integrates commits from parallel agent branches using sequential cherry-pick. Use after parallel work completes in isolated branches or worktrees.
The English summary is being prepared. Showing the original description.
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
The English summary is being prepared. Showing the original description.
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
The English summary is being prepared. Showing the original description.