i-doc-verify

Name: i-doc-verify
Availability: InStock
Author: kamo

Verify documentation fixes and check links in changed markdown files.

12|1|Updated Dec 27, 2025

Search Tags:#workflow #documentation #verification #review #docs #link-check

Ready to run

npx skills add https://github.com/apokamo/kaji --skill i-doc-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: i-doc-verify
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/i-doc-verify
Command: npx skills add https://github.com/apokamo/kaji --skill i-doc-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify documentation fixes after reviews to ensure previous feedback is resolved.

Core Features & Use Cases

Validation of previous review fixes: Confirms that earlier actionable feedback has been resolved in the docs.
Change quality checks: Performs link and reference checks on changed markdown files to prevent broken links and missing references.
Workflow integration: Integrates into the doc-review workflow between i-doc-fix and i-pr to gate release of documentation.

Quick Start

Run the i-doc-verify skill after i-doc-fix to confirm that previous issues are resolved.

Frequently Asked Questions about i-doc-verify

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

FAQPage Schema

How do I verify documentation fixes after a review to ensure previous feedback is resolved?▼

Documentation verification confirms that earlier actionable review feedback has been resolved in the docs. It validates prior issues are fixed and ensures no new problems are introduced during updates.

Can I check for broken links in changed markdown files during the documentation review workflow?▼

Yes, link checks on changed markdown files prevent broken links and missing references. This change quality check integrates directly into the documentation review workflow to gate updates.

What is the best way to gate the release of documentation updates after applying fixes?▼

Gating documentation release requires running verification after fixes are applied. This workflow integration validates that previous issues are resolved and no new problems are introduced before proceeding to release.

Does documentation verification require input validation before checking review fixes?▼

Yes, documentation verification enforces input validation before proceeding. This ensures the review feedback and changed markdown files meet the required criteria before performing link and reference checks.

How do I integrate doc verification into my existing documentation review workflow?▼

Doc verification integrates into the workflow by running after fixes are applied and before the pull request stage. It gates the release of documentation by confirming prior issues are resolved.

Why does documentation verification fail when new issues are introduced during markdown updates?▼

Documentation verification fails to prevent releasing new problems alongside fixes. It performs strict change quality checks on markdown files to ensure no new broken links or missing references are introduced.