skills.rest
muselesscreator
muselesscreatorCOMMUNITY
Explore all skills by this author →
GitHub

update-learnings

Re-analyzes changed repository files and updates stored flat-file learnings incrementally.

Updated Apr 9, 2026
Search Tags:#git#codebase analysis#diff#code patterns#incremental update#knowledge refresh#repository learnings
One-click install
npx skills add https://github.com/muselesscreator/ui-skills --skill update-learnings-muselesscreator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-learnings
Source: https://github.com/muselesscreator/ui-skills/tree/main/update-learnings
Command: npx skills add https://github.com/muselesscreator/ui-skills --skill update-learnings-muselesscreator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stored codebase learnings become stale as a repository evolves, forcing either outdated context or expensive full re-analysis. This Skill refreshes only what changed by diffing current code against previously stored learnings. ## Core Features & Use Cases - Incremental Re-Analysis: Uses git history since the last-analyzed date to identify changed files and re-analyzes only affected areas. - Read-Merge-Write Updates: Merges new findings into existing learning files (e.g., ui-patterns.md, gotchas.md), adding new patterns, removing resolved gotchas, and preserving still-accurate content. - Work-Repo Guard: Detects repos with a ./wiki/ directory and redirects to the /wiki-ingest workflow instead of flat learnings. - Use Case: After a sprint of changes to a UI component library, run this Skill to refresh only the affected pattern notes in ~/.claude/repo-learnings/{repo}/ without rewriting everything. ## Quick Start Ask the AI to update the learnings for this repository, optionally scoping the refresh to a specific path.

Frequently Asked Questions about update-learnings

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

FAQPage Schema
How do I update stale codebase learnings without re-analyzing everything?▼

Run the update-learnings workflow, which uses git log since the last-analyzed date to find changed files and re-analyzes only those areas. It then merges new findings into existing learning files rather than rewriting them from scratch.

How does incremental repo analysis detect what changed?▼

It reads the Last analyzed date from the stored index.md header, then runs git log --since with --name-only to list changed files. Changed components trigger re-analysis of their entire feature area.

Can I scope the learnings update to a specific directory?▼

Yes, pass an optional path argument to scope the re-analysis to that directory. Without an argument, the Skill analyzes changes across the whole repository.

When should I use wiki-ingest instead of updating flat learnings?▼

Use /wiki-ingest when the repository contains a ./wiki/ directory, since work-repo wikis are refreshed via SHA-based change detection in that workflow. The update-learnings Skill detects this case and exits with a redirect message.

What happens to existing learning notes during an update?▼

Existing notes are preserved through a read-merge-write process: new patterns are added, resolved gotchas are removed, stale content is updated, and accurate content is kept. The Last analyzed date is bumped in each updated file's header.

Related Skills

Explore More Software Engineering Skills→
catlog22catlog22
511

manage-learn

Append atomic learning insights to lessons.jsonl with stable INS-ids.

Community
Intermediate
tech-leads-clubtech-leads-club
5.1k

learning-opportunities

Offers interactive learning exercises after architectural coding work to build developer understanding.

Official
Intermediate
laris-colaris-co
2

project

Track external repositories and link them via flat symlinks.

Official
Intermediate
cajiascajias

uv-worktree-venv-fallthrough

Diagnoses uv run PYTHONPATH fallthrough issues in fresh git worktrees with empty virtual environments.

Community
Intermediate