learner

Extract post-merge learnings from pull requests into knowledge graph updates.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/agorokh/applied-ai-research --skill learner-agorokh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learner
Source: https://github.com/agorokh/applied-ai-research/tree/main/.cursor/skills/learner
Command: npx skills add https://github.com/agorokh/applied-ai-research --skill learner-agorokh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires CLAUDE_MEMORY_GATE.

What problem does it solve?

After a PR is merged, the team often loses valuable learnings that could prevent repeated fixes and improve enterprise-readiness over time.

Core Features & Use Cases

  • Tier-3 substrate first: Queries the canonical knowledge graph to avoid duplicating prior learnings and to ground updates in existing facts.
  • Evidence-to-knowledge extraction: Analyzes the merged PR diff and commit messages to propose concise updates to operational learned facts.
  • Safe knowledge promotion: Produces both Tier 1 updates in AGENTS.md and Tier 2 vault node suggestions with schema-valid frontmatter, tagging items as universal vs project-specific.
  • Guardrails for maintainers: Prevents secrets leakage and focuses on summarizing proposed edits for human acceptance, not silent replacement.

Quick Start

Run the learner skill after a PR is merged to extract post-merge learnings, update AGENTS.md learned workspace facts, and propose new or refined vault nodes based on the Tier-3 substrate query.

Frequently Asked Questions about learner

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

FAQPage Schema
How do I extract durable knowledge from merged pull requests?

To document pull request learnings, analyze the merged PR diff and commit messages to propose AGENTS.md updates and schema-valid vault nodes. It queries the knowledge graph first to avoid duplicating prior learnings and tags facts as universal or project-specific.

How does knowledge graph querying prevent duplicated documentation updates?

Knowledge graph querying prevents duplicated documentation updates by requiring a mandatory Tier-3 substrate query before extraction. This grounds proposed vault node creation and AGENTS.md edits in existing canonical facts, ensuring new learnings complement rather than repeat prior knowledge.

Can I use this to automatically update AGENTS.md for enterprise AI repository maintenance?

Yes, you can use this for enterprise AI repository maintenance. It analyzes merged PR diffs to propose concise AGENTS.md learned facts updates and vault node refinements, summarizing proposed edits for human acceptance rather than silent replacement.

Does the learner skill work without the CLAUDE_MEMORY_GATE dependency?

The learner skill requires the CLAUDE_MEMORY_GATE dependency to function. This prerequisite enables the mandatory Tier-3 knowledge graph queries needed to ground extracted learnings in existing canonical facts before proposing AGENTS.md or vault node updates.

What are the limitations of automated knowledge extraction from PR diffs?

Automated knowledge extraction from PR diffs has strict no-secrets constraints to prevent leakage. It focuses on summarizing proposed edits for human acceptance rather than silent replacement, meaning maintainers must review and approve all AGENTS.md and vault node updates.

What is the best way to maintain vault graph nodes after merging enterprise AI changes?

The best way to maintain vault graph nodes is to run the learner skill post-merge to propose new or refined Tier-2 nodes. It applies schema-valid frontmatter and tags updates as universal versus project-specific based on extracted PR learnings.