Consult Librarian

Blocks merges when src changes lack corresponding documentation updates.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/Row0902/agents --skill consult-librarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Consult Librarian
Source: https://github.com/Row0902/agents/tree/main/.agent/skills/consult_librarian
Command: npx skills add https://github.com/Row0902/agents --skill consult-librarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation drift occurs when code changes outpace written guidance, leading to outdated or missing docs and decision records.

Core Features & Use Cases

  • Documentation Synchronization: Verifies that updated modules have corresponding docs in docs/development/xxx.md and updates the task.md as needed.
  • Guardrails & Governance: Enforces a merge blocker when src changes without docs updates, ensuring code changes are always documented.
  • Auditing & Feedback: Generates Librarian Reports with Status (PASS/FAIL) and Gap/Action items to guide remediation.

Quick Start

Ask the Librarian to audit the latest code changes for documentation gaps and generate missing docs.

Frequently Asked Questions about Consult Librarian

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

FAQPage Schema
How do I prevent documentation drift during software development?

Prevent documentation drift by enforcing documentation alignment with code changes. A governance guard blocks merges when src changes lack corresponding docs updates, ensuring API and architecture modifications are always documented.

How do I enforce documentation updates in code review?

Enforce documentation updates in code review by applying a merge blocker that activates when src changes lack corresponding docs updates. It generates a DocScan checklist and Librarian Report with PASS/FAIL status and gap items to guide remediation.

What is documentation governance for architecture decisions?

Documentation governance for architecture decisions ensures code changes are paired with updated ADRs and module docs. It audits codebase updates, blocks undocumented merges, and provides feedback loops to maintain alignment between architecture decisions and records.

Can I automatically block merges when API changes lack docs updates?

Yes, you can block merges when API changes lack docs updates. The guardrail checks for corresponding updates in module docs and task.md, stopping the merge if documentation synchronization is incomplete.

How do I audit code changes for missing ADRs and docs?

Audit code changes for missing ADRs and docs by scanning the codebase for undocumented API or architecture updates. It generates a Librarian Report with Status and Gap/Action items to guide remediation of missing decision records.