librarian-update

Update a codebase graph by analyzing git diffs and source files.

Updated Aug 23, 2026

Search Tags:#git #documentation #refactoring #codebase #librarian #convention

Ready to run

npx skills add https://github.com/bert-berkers/UrbanRepML --skill librarian-update

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: librarian-update
Source: https://github.com/bert-berkers/UrbanRepML/tree/main/.claude/skills/librarian-update
Command: npx skills add https://github.com/bert-berkers/UrbanRepML --skill librarian-update

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of updating a codebase's structural graph, ensuring it accurately reflects recent changes and helps maintain a clear overview of the project's architecture.

Core Features & Use Cases

Codebase Graph Maintenance: Automatically updates a visual or textual representation of the codebase's modules, classes, functions, and dependencies.
Change Tracking: Analyzes git diff to identify and incorporate new, modified, or removed code components.
Convention Discovery: Scans for emerging coding patterns and conventions to aid in formalizing project standards.
Use Case: After a developer merges a new feature, running this Skill ensures the codebase documentation (e.g., codebase_graph.md) is immediately updated, preventing outdated information and aiding onboarding.

Quick Start

Run the librarian agent to update the codebase graph after recent changes.

Frequently Asked Questions about librarian-update

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

FAQPage Schema

How do I update codebase documentation after merging new git changes?▼

To update codebase documentation after merging git changes, analyze the git diff to identify modified modules, classes, and functions, then regenerate the structural graph to reflect new dependencies. This keeps architecture records current without manual tracking.

What is a codebase graph and how does it track refactoring?▼

A codebase graph is a structural representation of modules, classes, functions, and dependencies. It tracks refactoring by analyzing git diffs to document added, changed, or removed components, maintaining an accurate architectural overview.

How do I formalize emergent coding conventions in a refactoring project?▼

Formalize emergent coding conventions by scanning recent git diffs and source files for repeated patterns during refactoring. Identifying these conventions helps suggest formal project standards and document structural changes.

Can I track removed functions and dependencies using a git diff?▼

Yes, tracking removed functions and dependencies is possible by analyzing the git diff. It identifies deleted or modified code components, allowing you to update the codebase graph and keep structural documentation accurate.

What's the best way to maintain a codebase graph for an evolving codebase?▼

Maintain a codebase graph for an evolving codebase by analyzing git diffs after feature merges. This automatically updates the textual representation of modules and dependencies, preventing outdated architecture information.

Do I need a git repository to document codebase modules and dependencies?▼

Yes, a git repository is needed to document codebase modules and dependencies accurately. The process analyzes git diffs and reads source files to identify structural changes, ensuring the codebase graph reflects recent modifications.