learn

Extract reusable patterns from git history and observations into .atv/instincts/project.yaml.

50|14|Updated Mar 11, 2026

Search Tags:#git #patterns #knowledge #project-management #observations #instincts

Ready to run

npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill learn-all-the-vibes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/learn
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill learn-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract reusable patterns from recent work and convert them into actionable instincts that guide future development, reducing repeated decisions and speeding onboarding.

Core Features & Use Cases

Gather Evidence: Collect data from git history, diffs, tool observations, existing instincts, and documented solutions to build a knowledge base.
Analyze Patterns: Identify recurring techniques, decisions, and workflows, and assign confidence for each pattern.
Create or Update Instincts: Write or update .atv/instincts/project.yaml with atomic instincts (id, trigger, behavior, confidence, etc.).
Write Results: Persist insights back to the project's instincts store to influence subsequent sessions.
Report: Generate a summary of new and updated instincts for the team.

Quick Start

Run the Learn skill to extract patterns from your latest work and update the project's instincts.

Frequently Asked Questions about learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I extract reusable patterns from git history to improve project knowledge?▼

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.

What is the best way to convert resolved bug fixes into development instincts?▼

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.

When should I update project instincts during a development workflow?▼

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.

How do project instincts reduce repeated decisions during software engineering?▼

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.

Can I gather evidence from existing instincts alongside git history to analyze patterns?▼

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.

What limitations exist when extracting patterns from recent work for project management?▼

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.