docs

Audit and update GitHub repository documentation to match actual repository state.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/whilp/working --skill docs-whilp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/whilp/working/tree/main/skills/docs
Command: npx skills add https://github.com/whilp/working --skill docs-whilp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that documentation accurately reflects the current state of a GitHub repository, eliminating discrepancies and maintaining up-to-date information.

Core Features & Use Cases

  • Documentation Auditing: Checks the structure, usage examples, tool lists, phase descriptions, and permissions in documentation files.
  • Repo Comparison: Compares documentation against the actual repository structure, makefiles, and workflow files.
  • Fixing Inaccuracies: Corrects inaccuracies in documentation by editing files directly.
  • Status Reporting: Generates a report detailing changes made and the overall status of the documentation.

Quick Start

Run the 'docs' skill to audit and update the documentation files in your GitHub repository.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I audit documentation to match my GitHub repository state?

Documentation auditing compares your docs against the actual repository structure, makefiles, and workflow files. It checks structure, usage examples, tool lists, and permissions to find inaccuracies, then edits files directly to match the repository state.

What is the best way to fix inaccurate documentation in a GitHub repository?

Fixing inaccurate documentation involves comparing files against the actual repository structure and workflows. The process corrects inaccuracies by editing files directly and generates a status report detailing all changes made to align documentation with the repository.

Does the documentation audit check makefiles and workflow files?

Yes, the documentation audit compares files against the actual repository structure, makefiles, and workflow files. It specifically checks structure, usage examples, tool lists, phase descriptions, and permissions to ensure documentation accurately reflects the repository setup.

How do I generate a report of documentation changes in a repository?

Generating a report of documentation changes happens automatically after auditing and fixing files. The process edits inaccurate documentation directly and produces a status report detailing the specific changes made and the overall documentation health.

Can I use this to update documentation permissions and tool lists?

Yes, updating documentation permissions and tool lists is a core function. The audit specifically checks these elements against the actual repository state and corrects any inaccuracies by editing the documentation files directly to match.