aif-learn
Skill0 starsChanged 7 months agoMITView on GitHub
Capture a project learning to persistent storage. Saves to tools/learnings/ (JSONL) and optionally vault/memory/notes/.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- aif-analyzeSkill
- aif-enhanceSkill
- aif-evolveSkill
- aif-feedbackSkill
- aif-ingestSkill
- aif-pulseSkill
- aiframework-learnSkill
- aiframework-reviewSkill
- aiframework-shipSkill
- aif-readySkill
- aif-researchSkill
- aif-reviewSkill
- aif-shipSkill
- aif-statusSkill
- retroSkill
- sheal-askSkill
- sheal-checkSkill
- sheal-driftSkill
- sheal-retroSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 35
If the learning is significant (would affect future architecture decisions):
- Very specific: line 36
Create a note in vault/memory/notes/ with YAML frontmatter
- Very specific: line 41
If sheal is installed (command -v sheal), also save to sheal using the mapped category:
- Distinctive: line 55
After saving, emit a telemetry event with category and stack info (NEVER the actual learning text):
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/aif-learn — Capture Learning
Usage
/aif-learn "description of what was learned"
Step 0: Telemetry (silent, non-blocking)
aiframework-telemetry skill_invoked skill=aif-learn 2>/dev/null || trueStep 1: Classify
Determine category: bug, gotcha, pattern, or decision
Step 2: Save to learnings file
Append a JSON line to tools/learnings/aif-learnings.jsonl:
{"date": "YYYY-MM-DD", "category": "category", "summary": "one-line", "detail": "full explanation", "files": ["relevant/files"]}Step 3: Save to vault (if significant)
If the learning is significant (would affect future architecture decisions):
- Create a note in
vault/memory/notes/with YAML frontmatter - Or create a decision record in
vault/memory/decisions/using ADR format fromvault/templates/decision-record.md
Step 3b: Dual-write to sheal (if installed)
If sheal is installed (command -v sheal), also save to sheal using the mapped category:
- bug → failure-loop
- gotcha → missing-context
- pattern/decision → workflow
# Replace <sheal-category> with the mapped value from above
sheal learn add "the learning summary" --tags=relevant,tags --category=<sheal-category> --severity=medium --project . 2>/dev/null || trueThis ensures learnings are available to both aiframework (JSONL) and sheal (markdown).
Step 4: Telemetry — learning captured (silent, non-blocking)
After saving, emit a telemetry event with category and stack info (NEVER the actual learning text):
# Extract lang/framework from manifest if available
_lang=$(jq -r '.stack.language // "unknown"' .aiframework/manifest.json 2>/dev/null || echo "unknown")
_fw=$(jq -r '.stack.framework // "none"' .aiframework/manifest.json 2>/dev/null || echo "none")
aiframework-telemetry learning_captured category=<category> lang="$_lang" framework="$_fw" 2>/dev/null || trueStep 5: Confirm
Output: "Learning captured: [summary]"
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

