skills.rest
stoodder
stoodderCOMMUNITY
Explore all skills by this author →
GitHub

librarian

Automates documentation maintenance and verification by scanning codebase discrepancies and filing oversized changes as proposed specs.

1|Updated Jul 5, 2026
Search Tags:#documentation#codebase#verification#maintenance#automated PR
One-click install
npx skills add https://github.com/stoodder/materia --skill librarian-stoodder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: librarian
Source: https://github.com/stoodder/materia/tree/main/plugins/materia/skills/librarian
Command: npx skills add https://github.com/stoodder/materia --skill librarian-stoodder

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures the accuracy and consistency of living documentation by performing periodic maintenance and verification against the codebase.

Core Features & Use Cases

  • Doc Drift Sweep: Automatically scan and correct minor discrepancies between documentation and the codebase.
  • Proposed Spec Creation: Identify and file oversized documentation changes as proposed specs for further review.
  • Automated PR Creation: Open and auto-merge PRs for documentation fixes, reducing manual overhead.
  • Use Case: Regularly run this Skill to keep your project's documentation up-to-date with the latest code changes, minimizing the risk of drift and ensuring accurate information for all stakeholders.

Quick Start

Run the librarian skill to automatically scan and fix documentation drift.

Frequently Asked Questions about librarian

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

FAQPage Schema
How do I automate documentation maintenance and fix doc drift against my codebase?▼

Automated documentation maintenance is handled by scanning the codebase to identify minor discrepancies and automatically correcting living documentation. The process resolves minor doc drift directly and opens automated PRs for the fixes.

What is the best way to handle oversized documentation changes during a doc drift sweep?▼

Oversized documentation changes are identified and filed as proposed specs for further review. This ensures significant codebase updates are separated from automated PR creation and require manual verification before integration.

Can I automatically open and merge pull requests for documentation fixes?▼

Yes, automated PR creation opens and auto-merges pull requests for documentation fixes. This reduces manual overhead by automatically applying minor corrections to living documentation after verifying the codebase.

Does this doc drift verification require direct access to my codebase and documentation files?▼

Yes, verifying living documentation requires direct access to the codebase and documentation files. The process scans these files to compare current code logic against documented specs and corrects any discrepancies found.

When should I run an automated documentation verification sweep?▼

Run documentation verification regularly to keep your project's living documentation up-to-date with the latest code changes. Periodic maintenance minimizes the risk of drift and ensures accurate information across all stakeholders.

Related Skills

Explore More Software Engineering Skills→
meirmmeirm
13

generating-readmes

Generate README.md files from project structure and metadata.

Community
Intermediate
fumtas1kfumtas1k

retro

Analyze merged pull requests and generate documentation improvement PRs.

Community
Advanced
lucasadcapital-beeplucasadcapital-beep

doc-maintenance

Identifies documentation drift and proposes edits, then creates a branch and PR for review.

Community
Intermediate
windyskywindysky

moai-docs-generation

Generate documentation patterns from code for Sphinx, MkDocs, TypeDoc, and Nextra.

Community
Advanced