lrh-doc-work

Updates repository docs by analyzing merged pull requests/workstreams using Diataxis classification and automated validation.

1|Updated Apr 7, 2026

Search Tags:#automation #workflow #documentation #github #maintenance #diataxis

Ready to run

npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-doc-work

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lrh-doc-work
Source: https://github.com/xenotaur/logical_robotics_harness/tree/main/.claude/skills/lrh-doc-work
Command: npx skills add https://github.com/xenotaur/logical_robotics_harness --skill lrh-doc-work

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes references (resource) components.

What problem does it solve?

This skill solves the common issue of documentation drift, where technical updates, new features, or workflow changes are implemented in code but remain undocumented or stale in the repository's guides.

Core Features & Use Cases

Context-Aware Updates: Automatically identifies affected documentation based on merged PRs, resolved work items, or closed workstreams.
Diataxis Classification: Ensures updates are categorized correctly into Tutorials, How-to guides, Reference material, or Explanations.
Safety Gates: Includes human-in-the-loop confirmation and validation steps to ensure documentation quality before PR submission.

Quick Start

Invoke the lrh-doc-work skill by providing the URL of a recently merged pull request to automatically identify and update the relevant documentation.

Frequently Asked Questions about lrh-doc-work

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

FAQPage Schema

How do I keep documentation in sync with merged pull requests?▼

Keeping documentation in sync with merged pull requests involves analyzing recently merged work to map technical changes into Diataxis documentation quadrants, validating updates through linting, and proposing changes via a pull request.

How does Diataxis classification work for automated documentation updates?▼

Diataxis classification maps technical changes from merged work into four documentation quadrants: Tutorials, How-to guides, Reference material, and Explanations. This ensures structural consistency and accuracy when updating repository docs.

Do I need the GitHub CLI installed to automate repository documentation updates?▼

You need the GitHub CLI (`gh`) installed to automate repository documentation updates, as the skill depends on it to analyze merged pull requests and propose validated documentation changes via GitHub.

Can I validate documentation updates before submitting a pull request?▼

You can validate documentation updates before submitting a pull request through automated linting and testing, with human-in-the-loop confirmation gates ensuring documentation quality and accuracy prior to PR submission.

What is the best way to prevent documentation drift after landing code changes?▼

Preventing documentation drift after landing code changes is best achieved by automatically analyzing merged workstreams, mapping updates to Diataxis documentation quadrants, and validating linted changes before submitting a pull request.

Why does my repository documentation remain stale after merging new features?▼

Repository documentation remains stale after merging new features when technical updates are not automatically mapped to Diataxis documentation quadrants. Automating this analysis and validating updates via pull requests resolves the documentation drift.