doc-maintenance

Compare git commit history against README, SPEC, and PRODUCT files to resolve documentation drift.

Updated May 27, 2026
One-click install
npx skills add https://github.com/bychrisr/now-company --skill doc-maintenance-bychrisr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-maintenance
Source: https://github.com/bychrisr/now-company/tree/main/.agents/skills/doc-maintenance
Command: npx skills add https://github.com/bychrisr/now-company --skill doc-maintenance-bychrisr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of documentation drift, where project documentation becomes outdated as features are added, removed, or modified, leading to user confusion and inaccurate project specs.

Core Features & Use Cases

  • Drift Detection: Automatically compares git history against README, SPEC, and PRODUCT files to identify missing or obsolete information.
  • Automated PR Generation: Creates a dedicated branch and opens a pull request with minimal, factual edits to keep documentation in sync with the codebase.
  • Use Case: After a major release or a series of feature merges, use this skill to ensure that your roadmap, feature tables, and quickstart guides accurately reflect the current state of the project.

Quick Start

Run the doc-maintenance skill to audit the current repository documentation and open a pull request for any necessary factual updates.

Frequently Asked Questions about doc-maintenance

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

FAQPage Schema
How do I automate documentation drift detection in a git repository?

Documentation drift detection is automated by comparing recent git commit history against core project files. The process classifies code changes into feature, breaking, or structural categories to identify missing or obsolete information in README, SPEC, and PRODUCT files.

Can I automatically open a pull request to fix outdated README files?

Yes, you can automatically open a pull request to fix outdated README files. The process creates a dedicated branch and submits a pull request containing minimal, factual edits to keep your documentation in sync with the current codebase.

Do I need GitHub CLI integration to keep project specs in sync with code changes?

Yes, you need both git and GitHub CLI integration to keep project specs in sync with code changes. These dependencies are required to automate the branch creation and pull request submission steps after identifying documentation drift.

What is the best way to update SPEC and PRODUCT files after a major release?

The best way to update SPEC and PRODUCT files after a major release is auditing the git history for structural or breaking changes. This ensures your roadmap, feature tables, and quickstart guides accurately reflect the current project state.

When should I not use automated documentation maintenance?

You should not use automated documentation maintenance for subjective rewrites or stylistic changes. The process applies only minimal, factual updates based on classified code changes, making it unsuitable for comprehensive documentation overhauls or manual content generation.