One-click install
npx skills add https://github.com/ahostbr/liteharness --skill ls-librarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ls-librarian
Source: https://github.com/ahostbr/liteharness/tree/main/liteharness/catalog/skills/ls-librarian
Command: npx skills add https://github.com/ahostbr/liteharness --skill ls-librarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It detects and fixes drift between your workspace documentation (architecture docs, skill catalogs, and memory files) and the actual filesystem state of your codebase.

Core Features & Use Cases

  • Architecture doc verification: Checks that listed paths and counted items in architecture documents match what actually exists on disk.
  • Skill catalog consistency audit: Finds new, stale, or changed catalog entries by comparing on-disk skills and documents against the library configuration.
  • Memory integrity repair: Validates MEMORY.md indices and prunes or updates references that no longer exist or are outdated.
  • Dead reference elimination: Locates broken markdown links and removes them to prevent unverifiable claims.

Quick Start

Run the librarian to reconcile architecture docs, catalog entries, and memory against the current repository state.

Frequently Asked Questions about ls-librarian

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

FAQPage Schema
How do I fix documentation drift between architecture docs and the actual codebase?

To fix documentation drift, you run a synchronization process that measures discrepancies between architecture docs and the current filesystem, then applies deterministic edits to align the paths and item counts.

What is the best way to audit a skill catalog for stale or changed entries?

Auditing a skill catalog for stale entries involves comparing on-disk skills and documents against the library configuration to find new, stale, or changed entries, logging the deltas for review.

How do I repair broken markdown links and eliminate dead references in my workspace?

Eliminating dead references and broken markdown links requires a read-only filesystem scouting process to locate unverifiable claims, followed by deterministic edits that remove the broken paths.

How do I validate MEMORY.md indices and prune outdated memory references?

Validating MEMORY.md indices involves checking memory integrity by measuring discrepancies between stored references and the filesystem, then applying curated corrections to prune outdated entries.

When should I run a workspace health check for memory and catalog consistency?

You should run a workspace health check for memory and catalog consistency after significant code changes to measure and correct any drift that occurred during the modifications.

Does repository synchronization require any specific dependencies or components?

Repository synchronization for memory and docs requires no external dependencies or components, operating directly on the filesystem to apply curated corrections and generate a final report of deltas.