ia-md-docs

Update and verify Markdown documentation against the current codebase.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-md-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ia-md-docs
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-md-docs
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-md-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents outdated or hallucinated project documentation by forcing documentation changes to be verified against the actual codebase state before writing.

Core Features & Use Cases

  • Update AGENTS.md / CLAUDE.md by extracting verifiable claims from existing context files and reconciling them with the current repository structure and tooling.
  • Refresh README.md by detecting the stack from config files and regenerating only the standard sections while optionally preserving custom content.
  • Maintain CONTRIBUTING.md by updating only existing files (never auto-creating) while preserving policy decisions and surfacing merge advice when the workflow should live in AGENTS.md.

Quick Start

Ask the agent to update the project documentation for this repository, verifying AGENTS.md and README.md against the current codebase.

Frequently Asked Questions about ia-md-docs

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

FAQPage Schema
How do I update README.md and AGENTS.md to match my current codebase?

To update README.md and AGENTS.md to match your current codebase, the skill reads existing context files to extract verifiable claims, verifies them against repository state, and safely overwrites standard sections while optionally preserving custom content using dry-run or thorough modes.

What is the best way to prevent outdated or hallucinated project documentation?

The best way to prevent outdated or hallucinated project documentation is to force documentation changes to be verified against the actual codebase state before writing. This ensures README.md, AGENTS.md, and CLAUDE.md accurately reflect current tooling and repository structure.

How does documentation verification work in a monorepo?

Documentation verification in a monorepo works by discovering the workspace structure and reconciling extracted claims from context files against the current tooling and repository state. It updates AGENTS.md and CLAUDE.md by scanning the monorepo to ensure documentation matches the actual codebase.

Can I preserve custom README sections while regenerating standard documentation?

Yes, you can preserve custom README sections while regenerating standard documentation. The skill detects the project stack from config files, regenerates standard sections of README.md, and optionally preserves your custom content during the verification and update process.

Does updating CONTRIBUTING.md auto-create the file if it does not exist?

No, updating CONTRIBUTING.md does not auto-create the file if it does not exist. The skill only updates existing CONTRIBUTING.md or DOCS files, preserves policy decisions, and surfaces merge advice when the workflow should live in AGENTS.md.

What modes are available for reporting documentation changes?

Available modes for reporting documentation changes include dry-run, preserve, minimal, and thorough. These modes control how the skill verifies claims against the repository state and applies updates to CLAUDE.md, AGENTS.md, README.md, and CONTRIBUTING.md files.