learn

Extracting reusable patterns from git history involves collecting diffs and observations to identify recurring techniques, then writing them as instincts to `.atv/instincts/project.yaml` for future development guidance.

Converting resolved bugs into development instincts requires analyzing recent work patterns, assigning confidence scores to recurring decisions, and persisting those atomic instincts into the project's knowledge base.

Update project instincts after completing features, resolving bugs, or at session end to capture fresh evidence, ensuring the knowledge base remains current and accurately guides subsequent development tasks.

Project instincts reduce repeated decisions by storing analyzed patterns with triggers and behaviors in a YAML file, allowing future sessions to reference prior workflows and automatically apply established techniques.

Yes, gathering evidence combines git history, tool observations, documented solutions, and existing instincts to build a comprehensive knowledge base for identifying recurring workflows and assigning confidence.

Extracting patterns relies on available git history and documented observations; without recent commits or tool evidence, the analysis cannot generate accurate instincts or assign appropriate confidence values.